Bug 1949365

Summary:	[16.2] pcs on host patchset triggers a problem during FFU on IHA deployments
Product:	Red Hat OpenStack	Reporter:	Michele Baldessari <michele>
Component:	puppet-tripleo	Assignee:	Michele Baldessari <michele>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	jjoyce, jpretori, jschluet, lmiccini, slinaber, tvignaud
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	puppet-tripleo-11.6.2-2.20210428172107.5c76ddc.el8ost.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-15 07:13:57 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 Michele Baldessari 2021-04-14 06:38:20 UTC

Description of problem:
With the merging of the pcs on host patchset for 16.2 we are seeing a problem with FFUs on Instance HA environments.

Preamble: tripleo keeps the stonith-enabled cluster property set to false until step 5.

With the pcs on host patchset the enablement happens still at step 5 but it gets triggered during tripleo_ha_wrapper deployment task of cinder-volume which tries to restart the cinder-volume service (during the leapp of the first controller) and this hangs forever because pacemaker is in the following transition:
- stonith-fence_compute-fence-nova is configured
- pacemaker wants to call stonith on for controller-0 (which is probably dumb, but  it is unlikely we'll be able to change that in the right timeframe as it seems a potentially involved change in behaviour)
- Any other action, like cinder-volume restart in this case, is stuck and the FFU fails.

Comment 7 errata-xmlrpc 2021-09-15 07:13:57 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