Bug 1474226
| Summary: | [WALA][cloud] cloud-init dhclient-hook script has some unexpected side-effects on Azure | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Yuhui Jiang <yujiang> | |
| Component: | cloud-init | Assignee: | Ryan McCabe <rmccabe> | |
| Status: | CLOSED ERRATA | QA Contact: | Vratislav Hutsky <vhutsky> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.4 | CC: | aherr, borisb, brendand, cfeist, danis, dhill, eterrell, fdinitto, hkrijger, huzhao, jbadiapa, jgreguske, jherrman, jopoulso, lars, leiwang, mmagr, mrunge, paulmey, rmccabe, stephen.zarkos, tdrake, tom.asquith, wshi, yujiang, yuxisun | |
| Target Milestone: | rc | Keywords: | Regression, Triaged, ZStream | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | cloud-init-0.7.9-12.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
A regression was introduced in cloud-init-0.9.9-7 that caused dhclient and NetworkManager hook scripts to run on Microsoft Azure even when the cloud-init service was not enabled at boot. In this release, the bug is fixed. As a result, dhclient and NetworkManager hook scripts do not run on Azure when cloud-init is not enabled at boot.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1516941 1530127 1579237 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 14:05:07 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1451548, 1516941, 1530127, 1579237, 1692393, 1692914 | |||
Hi - Has there been any progress on this? We're building on Azure and this is an issue! (In reply to tom.asquith from comment #14) > Hi - Has there been any progress on this? We're building on Azure and this > is an issue! Hi tom,we are working on this issue,plz wait new build to post/release. Or if you need help right now,you can get help from our supporting team. Thanks! The scenario seems a bit odd to me, installing cloud-init and then disabling it. What is the intended purpose of installing cloud-init in this scenario? When cloud-init and WALA are both installed, the expectation is that cloud-init does provisioning and WALA takes a back seat for that. WALA will take care of extension handling later on. http://cloudinit.readthedocs.io/en/latest/topics/datasources/azure.html#walinuxagent Although there is also: https://github.com/Azure/WALinuxAgent/blob/master/config/ubuntu/waagent.conf#L8-L9 Thanks! Hi Paul Meyer, We open this issue because this is a "possible" but not a "must" scenario. The WALA and cloud-init packages are not conflict, which means customers can choose to use WALA or cloud-init to provision the VM(in other words, customer probably don't know or forget there's cloud-init in there image if the cloud-init service is disabled). Although we expect that customer install cloud-init only if they enable it, we cannot guarantee that. Currently, because of this issue, WALA skips provisioning even if "Provisioning.Enabled=y" "Provisioning.UseCloudInit=n" in waagent.conf and cloud-init service is disabled. Thanks! *** Bug 1516941 has been marked as a duplicate of this bug. *** Verify with cloud-init-0.7.9-19 in RHEL-7.5-20171215.0 in Azure. Result: Pass. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0806 |
Description of problem: I am responsible for testing Windows Azure Linux Agent(WALA) with RHEL on Azure.And recently we found that cloud-init has some side effects on WALA. cloud-init dhclient-hook script(/etc/NetworkManager/dispatcher.d/cloud-init-azure-hook) will always run on booting though cloud-init-local,cloud-init,cloud-config,cloud-final,these 4 services are disabled on booting.And inside the dhclient-hook script,it invoke "exec cloud-init dhclient-hook up "$1"".And this will affect WALA. In my opinion,the dhclient-hook script should invoke cloud-init when we need rather than always invoke cloud-init.That is to say,when cloud-init-local,cloud-init,cloud-config,cloud-final are disabled,dhclient-hook script shouldn't invoke cloud-init.And when 4 services are enabled,dhclient-hook script should do. Version-Release number of selected component (if applicable): WALinuxAgent-2.2.14-1 cloud-init-0.7.9-9 RHEL Version: RHEL-7.4 How reproducible: 100% Steps to Reproduce: 1. Install cloud-init package in VM, disable related services: # systemctl disable cloud-{init-local,init,config,final} 2. Deprovision the VM and use this os disk to create a new VM 3. Check VM status Actual results: cloud-init dhclient-hook script invoked cloud-init running,and caused WALA Provision failed. /var/log/waagent.log: 2017/07/21 02:46:16.396313 INFO Running default provisioning handler 2017/07/21 02:46:16.424520 ERROR cloud-init is running [PID 673, /usr/bin/python^@/usr/bin/cloud-init^@dhclient-hook^@up^@eth0^@] ... 2017/07/21 02:46:24.561451 ERROR Event: name=WALinuxAgent, op=Provision, message=[000004] cloud-init appears to be running, this is not expected, cannot continue 2017/07/21 02:46:24.569447 ERROR Provisioning failed: [000004] cloud-init appears to be running, this is not expected, cannot continue Expected results: cloud-init dhclient-hook script shoud exit while cloud-init services are disabled. Additional info: Refer to bug: https://bugzilla.redhat.com/show_bug.cgi