Public bug reported:
I am setting up a testing environment for Trusty, MAAS and juju, all on
KVM's. I provisioned 5 machines through MAAS and juju add-machine, all
went fine.
When the systems reboot - all 5 of them - the network configuration
fails and thus the cloud init. You get the "cloud-init-nonet wating for
120 seconds ..." and then the subsequent "gave up waiting ..." messages.
I added some outputs to cloud-init-nonet, for that the funny lines in
the boot.log. What is interesting that after all the wating and doing
things, finally you get a login prompt. And the network is up as it
should!
I added bridge_maxwait 0 to the br0 stanza in /etc/network/eth0.config,
but that does not change anything. Upstart job logs do not show any
errors.
I have tested the br0 configuration on a fresh 14.04 server installation
with no cloud features and it works without any changes.
I thought maybe firewall issues, so I removed ufw.conf for a change -
reboot was the same.
All used packages used are the latest 14.04 repositories, freshly
updated.
** Affects: cloud-init
Importance: Undecided
Status: New
** Tags: cloud-init juju maas
** Attachment added: "Systems boot.log"
https://bugs.launchpad.net/bugs/1345433/+attachment/4157688/+files/boot.log
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1345433
Title:
cloud-init network error when using MAAS/juju
Status in Init scripts for use on cloud images:
New
Bug description:
I am setting up a testing environment for Trusty, MAAS and juju, all
on KVM's. I provisioned 5 machines through MAAS and juju add-machine,
all went fine.
When the systems reboot - all 5 of them - the network configuration
fails and thus the cloud init. You get the "cloud-init-nonet wating
for 120 seconds ..." and then the subsequent "gave up waiting ..."
messages.
I added some outputs to cloud-init-nonet, for that the funny lines in
the boot.log. What is interesting that after all the wating and doing
things, finally you get a login prompt. And the network is up as it
should!
I added bridge_maxwait 0 to the br0 stanza in
/etc/network/eth0.config, but that does not change anything. Upstart
job logs do not show any errors.
I have tested the br0 configuration on a fresh 14.04 server
installation with no cloud features and it works without any changes.
I thought maybe firewall issues, so I removed ufw.conf for a change -
reboot was the same.
All used packages used are the latest 14.04 repositories, freshly
updated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1345433/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
