| 2014-01-15 22:35:00 |
Ben Howard |
bug |
|
|
added bug |
| 2014-01-15 22:35:08 |
Ben Howard |
cloud-init (Ubuntu): assignee |
|
Ben Howard (utlemming) |
|
| 2014-01-15 22:35:10 |
Ben Howard |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-01-15 22:35:14 |
Ben Howard |
cloud-init (Ubuntu): status |
New |
In Progress |
|
| 2014-01-15 22:40:24 |
Ben Howard |
description |
Upon 'capturing' a Ubuntu VM on Windows Azure, instances do not come up. This is caused by Azure re-using the wrong GUID.
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) |
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) |
|
| 2014-01-15 22:41:24 |
Ben Howard |
summary |
cloud-init uses incorrect GUID for instance ID |
cloud-init Azure Datasource does not detect new instance |
|
| 2014-01-15 22:42:11 |
Ben Howard |
attachment added |
|
Cloud-init log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949810/+files/cloud-init.log |
|
| 2014-01-15 23:21:45 |
Ben Howard |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949827/+files/cloud-init.log |
|
| 2014-01-16 00:20:43 |
Ben Howard |
branch linked |
|
lp:~utlemming/cloud-init/lp1269626 |
|
| 2014-01-16 00:20:57 |
Ben Howard |
nominated for series |
|
Ubuntu Precise |
|
| 2014-01-16 00:20:57 |
Ben Howard |
nominated for series |
|
Ubuntu Quantal |
|
| 2014-01-16 00:20:57 |
Ben Howard |
nominated for series |
|
Ubuntu Saucy |
|
| 2014-01-16 00:20:57 |
Ben Howard |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-02-10 20:16:30 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2014-02-14 20:07:40 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
In Progress |
Fix Released |
|
| 2014-02-18 18:38:00 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-init |
|
| 2014-03-18 17:32:51 |
Ben Howard |
branch linked |
|
lp:~utlemming/ubuntu/precise/cloud-init/lp1269626 |
|
| 2014-03-19 23:41:07 |
Ben Howard |
summary |
cloud-init Azure Datasource does not detect new instance |
[SRU] cloud-init Azure Datasource does not detect new instance |
|
| 2014-03-19 23:41:46 |
Ben Howard |
bug task added |
|
walinuxagent (Ubuntu) |
|
| 2014-03-19 23:42:18 |
Ben Howard |
bug task added |
|
cloud-init (Ubuntu Precise) |
|
| 2014-03-19 23:42:18 |
Ben Howard |
bug task added |
|
walinuxagent (Ubuntu Precise) |
|
| 2014-03-19 23:42:40 |
Ben Howard |
bug task added |
|
cloud-init (Ubuntu Saucy) |
|
| 2014-03-19 23:42:40 |
Ben Howard |
bug task added |
|
walinuxagent (Ubuntu Saucy) |
|
| 2014-03-19 23:42:49 |
Ben Howard |
bug task added |
|
cloud-init (Ubuntu Trusty) |
|
| 2014-03-19 23:42:49 |
Ben Howard |
bug task added |
|
walinuxagent (Ubuntu Trusty) |
|
| 2014-03-19 23:43:22 |
Ben Howard |
walinuxagent (Ubuntu Trusty): status |
New |
Fix Released |
|
| 2014-03-19 23:56:54 |
Ben Howard |
description |
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) |
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) |
|
| 2014-03-19 23:57:12 |
Ben Howard |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-03-21 16:26:29 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/cloud-init |
|
| 2014-03-21 16:44:18 |
Dave Walker |
cloud-init (Ubuntu Precise): status |
New |
Fix Committed |
|
| 2014-03-21 16:44:23 |
Dave Walker |
bug |
|
|
added subscriber SRU Verification |
| 2014-03-21 16:44:32 |
Dave Walker |
tags |
amd64 apport-bug trusty uec-images |
amd64 apport-bug trusty uec-images verification-needed |
|
| 2014-03-21 16:45:51 |
Dave Walker |
cloud-init (Ubuntu Saucy): status |
New |
Fix Committed |
|
| 2014-03-24 22:07:45 |
Ben Howard |
tags |
amd64 apport-bug trusty uec-images verification-needed |
amd64 apport-bug uec-images verification-done |
|
| 2014-03-31 06:45:09 |
Launchpad Janitor |
cloud-init (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2014-03-31 06:45:20 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2014-03-31 06:45:36 |
Launchpad Janitor |
cloud-init (Ubuntu Saucy): status |
Fix Committed |
Fix Released |
|
| 2014-12-05 07:04:05 |
Rolf Leggewie |
walinuxagent (Ubuntu Saucy): status |
New |
Won't Fix |
|
| 2021-10-14 01:47:56 |
Steve Langasek |
walinuxagent (Ubuntu Precise): status |
New |
Won't Fix |
|
