Description of problem:
cloud-init v18.2 removes 'NOZEROCONF=yes' from overcloud nodes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy overcloud nodes using an image in RHOSP13z3.
'NOZEROCONF=yes' doesn't exist in /etc/sysconfig/network.
'NOZEROCONF=yes' exists in /etc/sysconfig/network.
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.
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.
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.
Created attachment 1515501 [details]
A patch in Fedora.
*** Bug 1651171 has been marked as a duplicate of this bug. ***
Do you have any updates on this bugzilla?
(In reply to Keigo Noha from comment #15)
> Hi Eduardo,
> Do you have any updates on this bugzilla?
> Keigo Noha
I don't have any updates on this.
Looking forward on puiterwijk's opinions on this, though
Fix included in cloud-init-18.2-5.el7
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
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.