1762432 – [OSP16] fence_compute: IHA is not working any longer due to a change in behaviour of nova's service disabling [rhel-8.1.0.z]

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1762432 - [OSP16] fence_compute: IHA is not working any longer due to a change in behaviour of nova's service disabling [rhel-8.1.0.z]

Summary: [OSP16] fence_compute: IHA is not working any longer due to a change in behav...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	fence-agents
Sub Component:
Version:	8.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	8.0
Assignee:	Oyvind Albrigtsen
QA Contact:	pkomarov
Docs Contact:
URL:
Whiteboard:
Depends On:	1760213
Blocks:
TreeView+	depends on / blocked

Reported:	2019-10-16 17:42 UTC by Oneata Mircea Teodor
Modified:	2020-11-14 06:48 UTC (History)
CC List:	15 users (show)
Fixed In Version:	fence-agents-4.2.1-30.el8_1.1
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1760213
Environment:
Last Closed:	2019-12-05 16:44:00 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2019:4112	0	None	None	None	2019-12-05 16:44:01 UTC

Comment 3 pkomarov 2019-11-05 12:25:32 UTC

Verified , 

the IHA process is working as excpected:

(undercloud) [stack@undercloud-0 ~]$ ansible computeInstanceHA -b -mshell -a'rpm -q fence-agents-compute'


overcloud-novacomputeiha-0 | CHANGED | rc=0 >>
fence-agents-compute-4.2.1-30.el8_1.1.noarch

overcloud-novacomputeiha-1 | CHANGED | rc=0 >>
fence-agents-compute-4.2.1-30.el8_1.1.noarch

(overcloud) [stack@undercloud-0 ~]$ openstack server show osvm2|grep hypervisor_hostnam
| OS-EXT-SRV-ATTR:hypervisor_hostname | overcloud-novacomputeiha-0.redhat.local    


(overcloud) [stack@undercloud-0 ~]$ ansible overcloud-novacomputeiha-0 -b -mshell -a'virsh list'
[WARNING]: Found both group and host with same name: undercloud

overcloud-novacomputeiha-0 | CHANGED | rc=0 >>
 Id    Name                           State
----------------------------------------------------
 1     instance-0000000b              running

(overcloud) [stack@undercloud-0 ~]$ ansible overcloud-novacomputeiha-0 -b -mshell -a'echo b >/proc/sysrq-trigger'
[WARNING]: Found both group and host with same name: undercloud

overcloud-novacomputeiha-0 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: Shared connection to 192.168.24.30 closed.",
    "unreachable": true
}


#from the logs 
Nov 05 12:15:58 controller-2 pacemaker-schedulerd[25359] (stage6) 	warning: Scheduling Node overcloud-novacomputeiha-0 for STONITH
Nov 05 12:15:58 controller-2 pacemaker-schedulerd[25359] (native_stop_constraints) 	info: compute-unfence-trigger:0_stop_0 is implicit after overcloud-novacomputeiha-0 is fenced
Nov 05 12:15:58 controller-2 pacemaker-schedulerd[25359] (LogNodeActions) 	notice:  * Fence (reboot) overcloud-novacomputeiha-0 'remote connection is unrecoverable'
Nov 05 12:15:58 controller-2 pacemaker-schedulerd[25359] (LogAction) 	notice:  * Recover    overcloud-novacomputeiha-0           (      

Nov 05 12:16:00 controller-2 pacemaker-fenced    [25356] (call_remote_stonith) 	info: Requesting that 'controller-0' perform op 'overcloud-novacomputeiha-0 off' with 'stonith-fence_ipmilan-5254000cae5a' for pacemaker-controld.25360 (72s)


Nov 05 12:16:05 controller-2 pacemaker-attrd     [25358] (attrd_peer_update) 	info: Setting evacuate[overcloud-novacomputeiha-0.redhat.local]: (null) -> yes from controller-0

(overcloud) [stack@undercloud-0 ~]$ ansible overcloud-novacomputeiha-0 -b -mshell -a'virsh list'
[WARNING]: Found both group and host with same name: undercloud

overcloud-novacomputeiha-0 | CHANGED | rc=0 >>
 Id    Name                           State
----------------------------------------------------

(overcloud) [stack@undercloud-0 ~]$ ansible overcloud-novacomputeiha-1 -b -mshell -a'virsh list'
[WARNING]: Found both group and host with same name: undercloud

overcloud-novacomputeiha-1 | CHANGED | rc=0 >>
 Id    Name                           State
----------------------------------------------------
 1     instance-0000000b              running

(overcloud) [stack@undercloud-0 ~]$ openstack server show osvm2|grep hypervisor_hostnam
| OS-EXT-SRV-ATTR:hypervisor_hostname | overcloud-novacomputeiha-1.redhat.local

Comment 5 errata-xmlrpc 2019-12-05 16:44:00 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, 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-2019:4112

Note You need to log in before you can comment on or make changes to this bug.