** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1316475
Title:
[SRU] CloudSigma DS for causes hangs when serial console present
Status in Init scripts for use on cloud images:
Fix Released
Status in Openstack disk image builder:
Fix Released
Status in tripleo - openstack on openstack:
Invalid
Status in “cloud-init” package in Ubuntu:
Fix Released
Status in “cloud-init” source package in Trusty:
Fix Released
Bug description:
SRU Justification
Impact: The Cloud Sigma Datasource read and writes to /dev/ttyS1 if
present; the Datasource does not have a time out. On non-CloudSigma
Clouds or systems w/ /dev/ttyS1, Cloud-init will block pending a
response, which may never come. Further, it is dangerous for a default
datasource to write blindly on a serial console as other control plane
software and Clouds use /dev/ttyS1 for communication.
Fix: The patch queries the BIOS to see if the instance is running on
CloudSigma before querying /dev/ttys1.
Verification: On both a CloudSigma instance and non-CloudSigma instance with
/dev/ttys1:
1. Install new cloud-init
2. Purge existing cloud-init data (rm -rf /var/lib/cloud)
3. Run "cloud-init --debug init"
4. Confirm that CloudSigma provisioned while CloudSigma datasource skipped
non-CloudSigma instance
Regression: The risk is low, as this change further restrict where the
CloudSigma Datasource can run.
[Original Report]
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 3 (xid=0x7e777c23)
DHCPREQUEST of 10.22.157.186 on eth2 to 255.255.255.255 port 67
(xid=0x7e777c23)
DHCPOFFER of 10.22.157.186 from 10.22.157.149
DHCPACK of 10.22.157.186 from 10.22.157.149
bound to 10.22.157.186 -- renewal in 39589 seconds.
* Starting Mount network filesystems [ OK
]
* Starting configure network device [ OK
]
* Stopping Mount network filesystems [ OK
]
* Stopping DHCP any connected, but unconfigured network interfaces [ OK
]
* Starting configure network device [ OK
]
* Stopping DHCP any connected, but unconfigured network interfaces [ OK
]
* Starting configure network device [ OK
]
And it stops there.
I see this on about 10% of deploys.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1316475/+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
