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.
Bug 1706482 - [cloud-init][RHVM]cloud-init network configuration does not persist reboot [RHEL 8.2.0]
Summary: [cloud-init][RHVM]cloud-init network configuration does not persist reboot [R...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cloud-init
Version: 8.0
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: 8.2
Assignee: Eduardo Otubo
QA Contact: Huijuan Zhao
Jiri Herrmann
Depends On: 1593010 1750710
TreeView+ depends on / blocked
Reported: 2019-05-05 03:31 UTC by ldu
Modified: 2020-12-20 08:30 UTC (History)
30 users (show)

Fixed In Version: cloud-init-18.5-8.el8
Doc Type: Known Issue
Doc Text:
(See https://bugzilla.redhat.com/show_bug.cgi?id=1666961 )
Clone Of: 1593010
Last Closed: 2020-04-28 16:03:14 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1719 0 None None None 2020-04-28 16:03:43 UTC

Comment 5 Yaju Cao 2019-07-10 09:33:40 UTC
Remove needinfo in comment 3 since it has already been tested in https://bugzilla.redhat.com/show_bug.cgi?id=1593010#c74, and the issue still exist, so we need to continue working on the fix.

Comment 13 Huijuan Zhao 2020-02-19 03:46:52 UTC
Tested with cloud-init-18.5-10.el8 on RHV, the issue is gone.

Verified on:
- libvirt-3.9.0-14.el7.x86_64
- VM: RHEL8.0 + cloud-init-18.5-10.el8

Verification steps:
1. Create VM with RHEL 8.0 (register to rhsm, enable baseos/appstream repos)
2. Install cloud-init cloud-init-18.5-10.el8
3. Start the service and set it up permanently by 'systemctl enable --now cloud-init'.
4. Power off the vm and create template.
5. Create a new vm from the new template with the following cloud init parameters (by GUI): 'TZ: +13 Tonga, Network: static, NIC Name: eth0, IP:, MASK:, GW:'.
6. Start the vm and verify cloud-init parameters are as expected (by `ip a` and  `cat /etc/sysconfig/network-scripts/ifcfg-eth0`).
7. Power off the vm from engine and repeat step 6.


- Cloud-init parameters was remain as expected after vm is powered off and restarted.

Move the status to VERIFIED.

Comment 15 errata-xmlrpc 2020-04-28 16:03:14 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.