Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2211146

Summary:	ovnmeta ports got IP addresses few days after no-fixed-ip was set for these ports
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-neutron	Assignee:	Rodolfo Alonso <ralonsoh>
Status:	CLOSED DUPLICATE	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	chrisw, egarciar, ralonsoh, scohen, twilson
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-12 14:50: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:

Description Alex Stupnikov 2023-05-30 15:06:26 UTC

Description of problem:

This is a follow-up bug for bug #2178599: customer used workaround proposed in https://bugzilla.redhat.com/show_bug.cgi?id=2178599#c1 and dropped fixed IPs for ovnmeta ports using "openstack port set --no-fixed-ip". For some time everything worked as expected, but then fixed IPs were set again.

I will share extracts from logs and CLI outputs privately. 

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

How reproducible:
- Use "openstack port set --no-fixed-ip" to drop fixed IP addresses from ovnmeta ports
- Wait for some time
- Fixed IP addresses are set again

Expected results:
Fixed IP addresses are not set by Neutron after "openstack port set --no-fixed-ip" was executed

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=2178599

Comment 7 Elvira 2023-06-12 14:50:44 UTC

Closing as duplicated, please feel free to reopen if you feel like we are missing something. There is no better work around for this, if anyone needs to have this issue solved you would need to update to the next Z version. Thanks a lot!

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