Bug 1666617 - OVN metadata agent fails when using TLS Everywhere
Summary: OVN metadata agent fails when using TLS Everywhere
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z1
: 14.0 (Rocky)
Assignee: Emilien Macchi
QA Contact: Roman Safronov
URL:
Whiteboard:
Depends On: 1632745
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-16 08:30 UTC by Daniel Alvarez Sanchez
Modified: 2019-03-18 13:03 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060910.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1632745
Environment:
Last Closed: 2019-03-18 13:03:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 631159 0 None None None 2019-01-16 08:30:35 UTC
Red Hat Product Errata RHBA-2019:0446 0 None None None 2019-03-18 13:03:37 UTC

Comment 9 Roman Safronov 2019-02-18 10:40:41 UTC 
Verified on 14.0-RHEL-7/2019-02-07.1 
which uses openstack-tripleo-heat-templates-9.2.1-0.20190119154856.fe11ade.el7ost.noarch.rpm  
with TLS enabled, link to the tested build:
https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/networking-ovn/job/DFG-network-networking-ovn-14_director-rhel-virthost-3cont_2comp_1ipa-ipv4-geneve-tls/2/

Verified that instances are able to retrieve metadata by accessing to http://169.254.169.254.
Comment 10 Mikey Ariel 2019-02-20 12:44:29 UTC 
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Comment 12 errata-xmlrpc 2019-03-18 13:03:28 UTC 
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:0446
Note You need to log in before you can comment on or make changes to this bug.