RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug has been copied from bug #1474226 and has been proposed to be backported to 7.4 z-stream (EUS).

Verify with cloud-init-0.7.9-9.el7_4.2. Steps followed bug 1474226. Result: Pass.

(In reply to yuxisun from comment #4)
> Verify with cloud-init-0.7.9-9.el7_4.2. Steps followed bug 1474226. Result:
> Pass.

It looks like you forgot to flip the bug state to verified.

Created attachment 1379135 [details]
cloud-init.log

It looks like we're still having issues with that.   I've attached the cloud-init.log file of the VM where the issue was reproduced.

(In reply to David Hill from comment #7)
> It looks like we're still having issues with that.   I've attached the
> cloud-init.log file of the VM where the issue was reproduced.

Is this behavior different than the latest official RHEL 7.4 released build? This looks like it's another issue. This BZ was for side-effects that occurred as a result of dhcp and NM hooks running when cloud-init was disabled.

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/RHBA-2018:0166