Bug 1811995 - [DDF] We should also add FQDN or hostname under no_proxy section
Summary: [DDF] We should also add FQDN or hostname under no_proxy section
Keywords:
Status: CLOSED DUPLICATE of bug 1812349
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 16.0 (Train)
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Vlada Grosu
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-10 11:01 UTC by Direct Docs Feedback
Modified: 2020-03-16 17:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-16 17:27:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Direct Docs Feedback 2020-03-10 11:01:58 UTC 
We should also add hostname or FQDN under no_proxy section 

Reported by: rhn-support-ravsingh

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/director_installation_and_usage/preparing-for-director-installation#annotations:b2c0ee32-2b22-49ee-818e-fa8a7c82a13c
Comment 1 Ravi Singh 2020-03-10 11:04:56 UTC 
In OSP16 if we set push_destination: true in containers-prepare.yaml, by default undercloud will upload images to FQDN:8787 or I would say at undercloud.ctlplane.localdomain:8787[from my lab environment].

cat /etc/hosts | grep -i ctlplane
172.16.0.1 undercloud.ctlplane.localdomain undercloud.ctlplane
Comment 5 Dan Macpherson 2020-03-16 04:51:53 UTC 
Vlada,this is that duplicate of the BZ you're already working on. Feel free to close it as a duplicate.
Comment 6 Vlada Grosu 2020-03-16 17:27:23 UTC 
Thanks, Dan!

Now that the changes for BZ#1812349 are live on the customer portal, I am closing this ticket:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/director_installation_and_usage/index#configuring-an-undercloud-proxy

*** This bug has been marked as a duplicate of bug 1812349 ***
Note You need to log in before you can comment on or make changes to this bug.