Bug 2010243
| Summary: | [OSP16.1][OVN] disable dhcp after network creation not updated metadata | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Luigi Tamagnone <ltamagno> | |
| Component: | python-networking-ovn | Assignee: | Rodolfo Alonso <ralonsoh> | |
| Status: | CLOSED ERRATA | QA Contact: | Eduardo Olivares <eolivare> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 16.1 (Train) | CC: | apevec, dalvarez, jpretori, jveiraca, lhh, majopela, ralonsoh, scohen, shtiwari | |
| Target Milestone: | z8 | Keywords: | Triaged | |
| Target Release: | 16.1 (Train on RHEL 8.2) | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | python-networking-ovn-7.3.1-1.20211021113440.4e24f4c.el8ost | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2015620 2018424 (view as bug list) | Environment: | ||
| Last Closed: | 2022-03-24 11:01:44 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 2015620, 2018424 | |||
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 (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement 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-2022:0986 |
Description of problem: Disable DHCP on a provider network after the creation didn't change the metadata information. Version-Release number of selected component (if applicable): [rhosp-release] Red Hat OpenStack Platform release 16.1.6 GA (Train) [os-release] Red Hat Enterprise Linux 8.2 (Ootpa) 8.2 (Ootpa) Steps to Reproduce: 1. create a provider network with DHCP enabled 2. Disable DHCP on provider network 3. Launch an instance on this network, Openstack reserves an IP address in that network for the instance. However, the instance will never be reachable as it doesn't get its IP address configured. It didn't change if it is used config-drive or cloudinit for metadata propagation. Actual results: - In the case of the config drive, the network is labelled ipv4_dhcp: ~~~ "networks": [ { "id": "network0", "type": "ipv4_dhcp", "link": "tapxx-bf", "network_id": "xxx" } ~~ - In case of cloudinit, netplan: ~~~ network: ethernets: ens3: dhcp4: true match: macaddress: xxx set-name: ens3 version: 2 ~~~ However, the subnet to which these instances are attached has DHCP disabled: ~~~ $ openstack subnet show -f json xxx_subnet { "allocation_pools": [ { "start": "xxx", "end": "xxx" } ], "cidr": "xxx/21", "created_at": "2021-08-27T06:50:58Z", "description": "", "dns_nameservers": [ "xxx", "xxx" ], "enable_dhcp": false, "gateway_ip": "xxx", "host_routes": [], "id": "xxx", "ip_version": 4, "ipv6_address_mode": null, "ipv6_ra_mode": null, "location": { "cloud": "", "region_name": "xxx", "zone": null, "project": { "id": "xxx", "name": "admin", "domain_id": null, "domain_name": "Default" } }, "name": "xxx", "network_id": "xxx", "prefix_length": null, "project_id": "xxx", "revision_number": 1, "segment_id": null, "service_types": [], "subnetpool_id": null, "tags": [], "updated_at": "2021-09-27T09:40:15Z" } ~~~ Expected results: DHCP disable from metadata output