Deprovision breaks iDNS registration when using cloud-init
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
walinuxagent (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
SRU justification
Impact : Users who run "waagent --deprovision" and then capture/snapshot an image will not have the instance register with iDNS and subsiquently the instance will be unreachable.
This issue is caused by waagent changing the "send-hostname" parameter in the dhclient.
Fix : Applied upstream commit from https:/
Test Case :
- Launch instance
- Install walinuxagent from proposed
- Run "waagent --deprovision"
- Shutdown instance
- Run "azure vm shutdown <name>" with Azure CLI tool
- Run "azure vm capture <name> <new name>" with Azure CLI tool
- Launch new instance from <new name>
- Confirm that instance is accesable using DNS name
Regression : Low. The change fixes how waagent interacts with /etc/dhcp/
[ORIGNIAL BUG REPORT]
Hello,
This is a request to please backport this patch from the 1.4.1 agent:
https:/
Summary
The Ubuntu images in the Windows Azure gallery (except for 12.10) all use cloud-init for provisioning. This means that WALA provisioning and the hostname monitor are disabled via /etc/waagent.conf.
However, when a user runs 'waagent -deprovision' the agent will attempt to modify the 'send host-name' parameter dhclient.conf file to set the hostname to "localhost.
In the Ubuntu images this behavior is not necessary since dhclient is already configured to send its hostname to the DHCP server. This patch makes the agent a bit smarter about this and leaves dhclient.conf alone if it sees that it is already configured to send it's current hostname to the DHCP server.
description: | updated |
Moving bug from private to public.