Bug 2083120

Summary: [OSP 16.2] [OVN-DVR] [Overcloud BM] Baremetal worker getting 503 from ovs-metadata agent
Product: Red Hat OpenStack Reporter: Lucas Alvares Gomes <lmartins>
Component: python-networking-ovnAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: urgent Docs Contact:
Priority: high    
Version: 16.2 (Train)CC: aos-bugs, apevec, bdobreli, cjanisze, dasmith, eduen, eglynn, ekuris, imatza, jamsmith, jhakimra, jkreger, kchamart, ldenny, lhh, lmartins, ltamagno, majopela, m.andre, mdemaced, pprinett, sbauza, scohen, sgordon, stephenfin, ushkalim, vromanso
Target Milestone: z4Keywords: TestBlocker, Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-7.4.2-2.20220409154863.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2033953 Environment:
Last Closed: 2022-12-07 19:22:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2033953    
Bug Blocks: 2041364    

Comment 2 Lucas Alvares Gomes 2022-05-30 09:09:29 UTC 
Fix included in https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2028783

- [OVN] Add baremetal support with Neutron DHCP agent (rhbz#2033953)

...

Quick reminder, in order for it to work we also need:

1) To add the OVNMetadataAgent to the controller templates

2) Add OVNCMSOptions: "enable-chassis-as-gw" to the controller templates. This is how Neutron/OVN know where to schedule the external ports for the baremetal nodes.
Comment 8 Itay Matza 2022-11-15 14:57:05 UTC 
Verified with OCP 4.12.0-0.nightly-2022-11-07-181244 on top of RHOS-16.2-RHEL-8-20221104.n.0.

Verification steps:
1. Add the OVNMetadataAgent and OVNCMSOptions: "enable-chassis-as-gw" to the controller templates. (https://bugzilla.redhat.com/show_bug.cgi?id=2083120#c2)

2. Install RHOS-16.2-RHEL-8-20221104.n.0.

3. Create baremetal nodes and a corresponding flavor.

4. Install OCP 4.12.0-0.nightly-2022-11-07-181244 using the baremetal flavor on top of the OSP.

5. Make sure the OCP cluster is up using the baremetal workers, and the bmaremetal workers can access the metadata:
```
	$ openstack baremetal node list
	+--------------------------------------+---------+--------------------------------------+-------------+--------------------+-------------+
	| UUID                                 | Name    | Instance UUID                        | Power State | Provisioning State | Maintenance |
	+--------------------------------------+---------+--------------------------------------+-------------+--------------------+-------------+
	| 132631d8-e7d9-4bce-a2cd-d3ad469fdef1 | titan25 | 9ad4cc2e-3a80-43f8-833d-597193e66f12 | power on    | active             | False       |
	| 8e00636c-bbe6-42cd-9455-679de10079f3 | titan26 | 1fe8038d-8943-4f76-89bc-79731a1a1a52 | power on    | active             | False       |
	+--------------------------------------+---------+--------------------------------------+-------------+--------------------+-------------+
	$ . shiftstackrc 
	$  openstack server list
	+--------------------------------------+-----------------------------+--------+---------------------------+--------------------+-----------+
	| ID                                   | Name                        | Status | Networks                  | Image              | Flavor    |
	+--------------------------------------+-----------------------------+--------+---------------------------+--------------------+-----------+
	| 1fe8038d-8943-4f76-89bc-79731a1a1a52 | ostest-rkktx-worker-0-h6988 | ACTIVE | provisioning=172.27.7.199 | ostest-rkktx-rhcos | baremetal |
	| 9ad4cc2e-3a80-43f8-833d-597193e66f12 | ostest-rkktx-worker-0-mdzfk | ACTIVE | provisioning=172.27.7.196 | ostest-rkktx-rhcos | baremetal |
	| 9d394670-be83-4989-8933-6b39bc7f5721 | ostest-rkktx-bootstrap      | ACTIVE | provisioning=172.27.7.193 | ostest-rkktx-rhcos | m4.xlarge |
	| 256eb40e-ed31-491e-9063-745216f1da88 | ostest-rkktx-master-2       | ACTIVE | provisioning=172.27.7.184 | ostest-rkktx-rhcos | m4.xlarge |
	| e3db07b5-ccf4-48ff-afca-c5c7f7e614f3 | ostest-rkktx-master-1       | ACTIVE | provisioning=172.27.7.188 | ostest-rkktx-rhcos | m4.xlarge |
	| 414b84af-1fd5-4205-a6f5-941ac5c4c4a5 | ostest-rkktx-master-0       | ACTIVE | provisioning=172.27.7.180 | ostest-rkktx-rhcos | m4.xlarge |
	+--------------------------------------+-----------------------------+--------+---------------------------+--------------------+-----------+
	$ ssh core.7.199
	Warning: Permanently added '172.27.7.199' (ECDSA) to the list of known hosts.
	Red Hat Enterprise Linux CoreOS 412.86.202211050206-0
	  Part of OpenShift 4.12, RHCOS is a Kubernetes native operating system
	  managed by the Machine Config Operator (`clusteroperator/machine-config`).

	WARNING: Direct SSH access to machines is not recommended; instead,
	make configuration changes via `machineconfig` objects:
	  https://docs.openshift.com/container-platform/4.12/architecture/architecture-rhcos.html

	---
	Last login: Tue Nov 15 13:31:26 2022 from 172.27.7.9
	[core@ostest-rkktx-worker-0-h6988 ~]$ curl http://169.254.169.254/openstack
	2012-08-10
	2013-04-04
	2013-10-17
	2015-10-15
	2016-06-30
	2016-10-06
	2017-02-22
	2018-08-27
```
Comment 15 errata-xmlrpc 2022-12-07 19:22: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 (Release of components for Red Hat OpenStack Platform 16.2.4), 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-2022:8794