Public bug reported:
This is a similar bug to bug 1225922.
but this is more just the first part.
The user can provide networking information to cloud-init via a local
datasource.
However, if there is networking information already, those devices might
already be up.
The suggested fix here is to block networking from coming up until after
cloud-init-local is up.
This way, a local datasource can reliably insert definitive networking
and not have to fight with information already present (such as default
'eth0' network info).
** Affects: cloud-init
Importance: Undecided
Status: New
--
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/1368861
Title:
networking comes up parallel to cloud-init-local
Status in Init scripts for use on cloud images:
New
Bug description:
This is a similar bug to bug 1225922.
but this is more just the first part.
The user can provide networking information to cloud-init via a local
datasource.
However, if there is networking information already, those devices might
already be up.
The suggested fix here is to block networking from coming up until
after cloud-init-local is up.
This way, a local datasource can reliably insert definitive networking
and not have to fight with information already present (such as
default 'eth0' network info).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1368861/+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
