Bug 2074815 - No DNS nameserver configured on computes when running overcloud deploy
Summary: No DNS nameserver configured on computes when running overcloud deploy
Keywords:
Status: CLOSED DUPLICATE of bug 2068489
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.0 (Wallaby)
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-13 07:28 UTC by Ricardo Diaz
Modified: 2022-04-13 09:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 09:57:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-14649 0 None None None 2022-04-13 07:45:02 UTC

Description Ricardo Diaz 2022-04-13 07:28:57 UTC
Description of problem:

When running "openstack overcloud deploy" there is no any nameserver configured in /etc/resolv.conf so names cannot be resolved.

Version-Release number of selected component (if applicable):
17


How reproducible:
100%

Steps to Reproduce:
1.Deploy the overcloud
2.
3.

Actual results:
No name servers in /etc/resolv.conf

Expected results:
Name servers (defined in configuration files) present in /etc/resolv.conf  

Additional info:
$ cat /etc/resolv.conf 
# Generated by NetworkManager
(no more lines)

Comment 2 Brendan Shephard 2022-04-13 09:52:55 UTC
Hey,

This one is known. It needs to be defined in the undercloud.conf file in OSP17. The THT parameter wont work with the new provisioning method and it will be removed:
https://review.opendev.org/c/openstack/tripleo-heat-templates/+/835247

I believe this BZ is a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=2068489

Comment 3 Brendan Shephard 2022-04-13 09:57:10 UTC

*** This bug has been marked as a duplicate of bug 2068489 ***


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