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

Bug 1942523

Summary:	[16.x] After a minor update on composable control plane we can be left with lingering ban on the ovn-dbs VIP
Product:	Red Hat OpenStack	Reporter:	Michele Baldessari <michele>
Component:	openstack-tripleo-heat-templates	Assignee:	Damien Ciabrini <dciabrin>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	lmiccini, mburns
Target Milestone:	beta	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.5.1-2.20210506094805.28ae385.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1968522 (view as bug list)		Environment:
Last Closed:	2021-09-15 07:13:08 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:	1968522

Description Michele Baldessari 2021-03-24 13:53:40 UTC

Description of problem:
Seen this sometimes via our nightly OSP16 job. http://10.19.227.133:8080/job/osp16_nightly_new/27/

Basically the controller replacement, succeeds but the tempest afterwards fail on networking problems.

The reason is that the OVN-DBS VIP is in Stopped state. It is in stopped state due to a ban on a node. Likely a leftover from our minor update process where we do ban/unban VIPs to minimize downtime:
[root@controller-1 ~]# pcs constraint ref ip-172.17.1.44
Resource: ip-172.17.1.44
  colocation-ip-172.17.1.44-ovn-dbs-bundle-INFINITY
  location-ip-172.17.1.44
  cli-ban-ip-172.17.1.44-on-controller-2
  order-ovn-dbs-bundle-ip-172.17.1.44-Optional

The controller-2 ban is what is problematic. If ovn-dbs runs as Master on controller-2 then the VIP will just not start.

Comment 8 errata-xmlrpc 2021-09-15 07:13:08 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 (Red Hat OpenStack Platform (RHOSP) 16.2 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/RHEA-2021:3483