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.
DescriptionMircea Vutcovici
2021-02-25 23:24:35 UTC
Description of problem:
This bug is similar with https://bugzilla.redhat.com/show_bug.cgi?id=1748015
However the cloud-init is the same version as the one in https://access.redhat.com/errata/RHSA-2020:3898
Version-Release number of selected component (if applicable):
- NetworkManager-1.18.8-2.el7_9.x86_64
- cloud-init-19.4-7.el7_9.2.x86_64
- Red Hat OpenStack Platform 13
How reproducible:
Steps to Reproduce:
1. deploy overcloud
2. restart controllers
Actual results:
$ cat /etc/resolv.conf
# Generated by NetworkManager
search example.com
$
Expected results:
$ cat /etc/resolv.conf
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
search example.com
nameserver 10.91.70.84
nameserver 10.113.103.212
$
Hi Amy,
Yes, I think that BZ#1903146 is matching the same symptoms.
Also the workaround mentioned in https://access.redhat.com/solutions/5837741 is present in openstack-tripleo-heat-templates-8.4.1-86.el7ost.noarch.rpm package:
[supportshell.prod.useraccess-us-west-2.redhat.com] [14:39:02+0000]
[mvutcovi@supportshell openstack-tripleo-heat-templates-8.4.1-86.el7ost.noarch]$ grep -rA8 "dns.*=.*none"
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2: - name: Set 'dns=none' in /etc/NetworkManager/NetworkManager.conf
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- ini_file:
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- path: /etc/NetworkManager/NetworkManager.conf
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- state: present
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- no_extra_spaces: true
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- section: main
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- option: dns
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- value: none
usr/share/openstack-tripleo-heat-templates/common/deploy-steps.j2- backup: true
I think you can mark the BZ as duplicate of BZ#1903146.
Thank you,
Mircea
Hi Mircea,
Got it, thanks for your confirmation.
Close this bug as duplicate of BZ#1903146.
*** This bug has been marked as a duplicate of bug 1903146 ***