** Description changed: + SRU Justification + + [IMPACT] Capturing a Windows Azure Linux instance controlled by Cloud- + init will result in any future instance based on it to fail to boot. + + Since booting on Windows Azure for Ubuntu is controlled via Cloud-init + and WALinuxAgent, there are two causes. + + [WALinuxAgent Issue]: Sends old hostname on captured instances + In version 1.4.2, WALinuxagent changed the dhclient configuration to send the right hostname via DHCP to the fabric. The current version of WALinuxAgent configures DHCP to send the old hostname. Since the fabric never receives a request for the new host name, the VIP for the new instance is never opened. Users will see "Connection refused" when attempting to connect to the instance. + + [WALinuxAgent Regression Potentional]: Low. This change simply changes + "send host-name <hostname>" to "send host-name = gethostname();" on + Windows Azure instances. + + [Cloud-init Issue]: Race condition on captured instances + Cloud-init configures Windows Azure by triggering WALinuxAgent's waagent daemon. The daemon goes off and gathers some files from the fabric, which takes a few seconds. Cloud-init, after firing off the agent, waits for the file SharedConfig.xml to land on disk. In the event of an instance being captured, Cloud-init files off the waagent daemon but then immediately finds the old SharedConfig.xml, resulting in Cloud-init seeing the old instance XML. Thus, the new instance is not provisioned. + + [Cloud-init Regression Potential]: Low. The change here detects if the + machine is a new instance by the precense of the ovf-env.xml file; if + the file exists, then SharedConfig.xml is removed. WALinuxAgent will + fetch a new one. Further, this file is not required unless the instance + is new. + + [Test case] + 1. Install new walinuxagent + 2. Install new cloud-init + 3. Shutdown instance + 4. Capture instance + 5. Launch new instance from captured instance + 6. The instance should responds via the network + + + [ORIGINAL REPORT] + Upon 'capturing' a Ubuntu VM on Windows Azure, instances do not come up. It appears that the cause is that Cloud-init is not looking at any datasources. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cloud-init 0.7.5~bzr902-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Uname: Linux 3.13.0-2-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Wed Jan 15 22:29:49 2014 PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269626 Title: [SRU] cloud-init Azure Datasource does not detect new instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
