Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
cloud-init v18.2 removes 'NOZEROCONF=yes' from overcloud nodes.
Version-Release number of selected component (if applicable):
cloud-init-18.2-1.el7_6.1.x86_64
How reproducible:
Every deployment.
Steps to Reproduce:
1. Deploy overcloud nodes using an image in RHOSP13z3.
2.
3.
Actual results:
'NOZEROCONF=yes' doesn't exist in /etc/sysconfig/network.
Expected results:
'NOZEROCONF=yes' exists in /etc/sysconfig/network.
Additional info:
Comment 4Ricardo J. Barberis
2018-12-13 14:50:39 UTC
Hello,
We have an old OpenStack installation (Icehouse) and we need 'NOZEROCONF=yes' to prevent having a 169.254.0.0 route and be able to reach OpenStack's metadata service.
I found a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1558641) in which Fedora applied a patch to cloud-init 17.1 to avoid this overwriting.
I applied that patch to cloud-init-18.2-1.el7.centos.1.src.rpm and recompiled it and now it doesn't overwrite /etc/sysconfig/network anymore.
BTW, I see this bug is marked as NEEDINFO. What info is needed? Maybe I can help.
Hello Ricardo,
Thank you for your comment on this bugzilla. It is really helpful for us.
It seems that the fix in RHBZ#1558641 might be changed between cloud-init-18.2 and cloud-init-17.
I'm checking the changelogs in cloud-init.
And needinfo means that someone requests an information or opinion onto his/her comment.
Best Regards,
Keigo Noha
Hello Eduardo,
The fix for cloud-init-17.1-4.fc28 for not changing default network configuration is not merged into the upstream.
I put patch in Fedora's package into this bugzilla.
Best Regards,
Keigo NOha
(In reply to Keigo Noha from comment #15)
> Hi Eduardo,
>
> Do you have any updates on this bugzilla?
>
> Regards,
> Keigo Noha
I don't have any updates on this.
Looking forward on puiterwijk's opinions on this, though
Comment 36Miroslav Rezanina
2019-03-25 14:07:10 UTC
Workaround: we were able to overcome this issue by downgrading cloud-init to v 0.7.9.
Temporary solution: install cloud-init 0.7.9 instead of cloud-init 18.2
BR, Alex.
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-2019:2123