[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
I simply issued sudo reboot and this happened. So I assume then that I have a different issue from the original reporter? Should I open a separate bug and stop polluting this one? In the meantime I'll pull the requested config files. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
/etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto juju-br0 iface juju-br0 inet dhcp bridge_ports eth0 /etc/network/interfaces.d is empty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Same as comment #44 I'm running hardware MAAS and I get this on every deployment. If I let cloud-init error out I can get logged in and juju- br0 is up by that point but it doesn't come up until after cloud-init tries to do it's stuff. This makes the nodes I deploy unusable. I'm going to see if I can come up with a fix and I'll post here if I do. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@dimitern Thanks for the swift reply. I'll do this now, for your information I'm currently running juju 1.21-beta3-trusty-amd64 from the juju-proposed ppa. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Also I've found that if I edit /etc/init/networking.conf and change the starts on line to:- starts on stopped cloud-init-local Then everything works fine although I realise that this is a very poor solution. Best I could manage with my limited upstart knowledge. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@dimitern Quite right, it is the devel branch I'm using. I was trying to find a new version which might already have a fix. I'm not very up on building software based on go. I'm getting the following when I try to run go install -v launchpad.net/juju-core/... go build launchpad.net/juju-core/... # launchpad.net/juju-core/testing/filetesting testing/filetesting/filetesting.go:194: cannot use checkers.Satisfies (type check.Checker) as type gocheck.Checker in function argument: check.Checker does not implement gocheck.Checker (wrong type for Info method) have Info() *check.CheckerInfo want Info() *gocheck.CheckerInfo # launchpad.net/juju-core/worker/uniter/charm worker/uniter/charm/bundles.go:52: cannot use err (type *error) as type error in function argument: *error is pointer to interface, not interface # launchpad.net/juju-core/utils/ssh utils/ssh/ssh_gocrypto.go:84: undefined: ssh.ClientConn make: *** [build] Error 2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Here is the bootstrap log created when I run juju bootstrap --to db2.ed1.mavennetwork.co.uk --debug ~/maas-bootstrap.log ** Attachment added: maas-bootstrap.log https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282230/+files/maas-bootstrap.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
And these are the juju and cloud logs from the node which was bootstrapped. This node is working fine right now but once it is rebooted I will get the cloud-init problem. I'll reboot it now and then post the logs after the problematic boot. ** Attachment added: logs.zip https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282231/+files/logs.zip -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
And lastly the logs from the node after it is rebooted. On this boot it takes a very long time to come up as cloud-init waits for the network bridge to come up and then eventually errors out. ** Attachment added: logs2.zip https://bugs.launchpad.net/juju-core/+bug/1271144/+attachment/4282232/+files/logs2.zip -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 929848] Re: init script has hard coded chown
I also have had a problem with this. In my case I had changed the user that apache runs as to make it compatible with freePBX which requires apache to run as the asterisk user. I have created an edited version of the init script which you will find attached. This appears to work with whatever you specify in the nagios config. Best check it over though as this is my first init script. I only changed lines 91,92 and 125. ** Attachment added: Altered init script https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/929848/+attachment/2936064/+files/nagios3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/929848 Title: init script has hard coded chown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/929848/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
