This is fixed in revision 437.
** Changed in: cloud-init
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/832175
Title:
Doesn't report an
** Changed in: cloud-init
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/832175
Title:
Doesn't report an error when hostname fails
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/832175
Title:
Doesn't report an error when hostname fails
To manage notifications about
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/832175
Title:
Doesn't report an error when hostname fails
To manage notifications about this bug
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu16
---
cloud-init (0.6.1-0ubuntu16) oneiric; urgency=low
* catch up with trunk at revision 439
* warn on failure to set hostname (LP: #832175)
* properly wait for all static interfaces to be up before
cloud-init
This is most relevant when something else is buggy as in bug 820962.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Low
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in:
