-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-8.10
-
None
-
Yes
-
None
-
rhel-ha
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
After updating a Pacemaker cluster, portblock RA monitoring operations continually failed and caused continuous flapping until monitoring operations were disabled for all portblock resources.
What is the impact of this issue to you?
High availability fails and breaks Pacemaker functionality after routine system updates.
Please provide the package NVR for which the bug is seen:
resource-agents-4.9.0-54.el8_10.20.x86_64
* Tue Oct 21 2025 Oyvind Albrigtsen <oalbrigt@redhat.com> - 4.9.0-54.20 - portblock: add promotable support, and method and status_check parameters Resolves: RHEL-116150
How reproducible is this bug?:
Very.
Steps to reproduce
- Use portblock resource agents (with monitoring operations enabled / default).
- Update systems (dnf update -y) or start with a freshly updated system before enabling portblock.
Expected results
Normal Pacemaker cluster operation.
Actual results
Continuous flapping:
Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating stop operation p_iscsi_portblock_off_target_vmdata_stop_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating stop operation p_lun_iscsi-0_stop_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating stop operation p_iscsi_target_vmdata_stop_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating stop operation p_iscsi_vip_vmdata_stop_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating stop operation p_iscsi_portblock_on_target_vmdata_stop_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating start operation p_iscsi_portblock_on_target_vmdata_start_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating monitor operation p_iscsi_portblock_on_target_vmdata_monitor_20000 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating start operation p_iscsi_vip_vmdata_start_0 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating monitor operation p_iscsi_vip_vmdata_monitor_10000 on olvm-0.example.com Nov 07 14:29:29 pacemaker-controld[1513]: notice: Initiating start operation p_iscsi_target_vmdata_start_0 on olvm-0.example.com Nov 07 14:29:30 pacemaker-controld[1513]: notice: Initiating monitor operation p_iscsi_target_vmdata_monitor_20000 on olvm-0.example.com Nov 07 14:29:30 pacemaker-controld[1513]: notice: Initiating start operation p_lun_iscsi-0_start_0 on olvm-0.example.com Nov 07 14:29:30 pacemaker-controld[1513]: notice: Initiating monitor operation p_lun_iscsi-0_monitor_20000 on olvm-0.example.com Nov 07 14:29:30 pacemaker-controld[1513]: notice: Initiating start operation p_iscsi_portblock_off_target_vmdata_start_0 on olvm-0.example.com Nov 07 14:29:30 pacemaker-controld[1513]: notice: Initiating monitor operation p_iscsi_portblock_off_target_vmdata_monitor_20000 on olvm-0.example.com
In this particular cluster, highly available iSCSI was unavailable due to issues with the updated portblock resource agent.
