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

Bug 2257991

Summary:	Duplicate Chassis/Chassis_Private rows not deleted by MaintenanceWorker
Product:	Red Hat OpenStack	Reporter:	Terry Wilson <twilson>
Component:	openstack-neutron	Assignee:	Terry Wilson <twilson>
Status:	CLOSED ERRATA	QA Contact:	Bharath M V <bmv>
Severity:	medium	Docs Contact:
Priority:	high
Version:	17.1 (Wallaby)	CC:	asyedham, bmv, chrisw, egarciar, froyo, mariel, scohen
Target Milestone:	z4	Keywords:	Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-18.6.1-17.1.20240726190742.85ff760.el9ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-11-21 09:39:25 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 Terry Wilson 2024-01-12 01:01:17 UTC

Description of problem:
If redeploying a host causes there to be multiple Chassis/Chassis_Private entries with the same hostname, neutron tries to clean those up to prevent issues. In the backport of this patch to 17.1, this doesn't happen due to remove_duplicated_chassis_register's checking for the existance of the Chassis_Private table and it not existing due to not being registered in the BaseOvnSbIdl class.

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

How reproducible: 100%


Steps to Reproduce:
1. Deploy
2. Create a Chassis entry with ovn-sbctl that has an existing hostname
3. Wait 5 minutes (the time interval of the periodic check) and run ovn-sbctl --no-leader-only find Chassis hostname=$existing_hostname

Actual results:
There will be two entries

Expected results:
The older Chassis/Chassis_Private entry will be deleted and there will be just one entry


Additional info:

Comment 13 errata-xmlrpc 2024-11-21 09:39:25 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 (RHOSP 17.1.4 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-2024:9974