Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1983196

Summary: --force-start, --force-stop, --force-monitor etc. with bundles
Product: Red Hat Enterprise Linux 9 Reporter: Ken Gaillot <kgaillot>
Component: pacemakerAssignee: Ken Gaillot <kgaillot>
Status: CLOSED CURRENTRELEASE QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 9.0CC: cluster-maint, cluster-qe, jmarcian, msmazova, tojeline
Target Milestone: betaKeywords: Triaged
Target Release: 9.0 BetaFlags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pacemaker-2.1.0-10.el9 Doc Type: No Doc Update
Doc Text:
This change is self-explanatory and doesn't need to be called out
Story Points: ---
Clone Of: 1447918 Environment:
Last Closed: 2021-12-07 21:57:54 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: 2.1.1
Embargoed:
Bug Depends On: 1447918    
Bug Blocks:    

Comment 1 Ken Gaillot 2021-07-16 19:44:02 UTC
crm-resource --force-* outputs an error message for bundles as of upstream master branch commit 5bcab230

Comment 7 Markéta Smazová 2021-09-16 08:56:54 UTC
before fix
-----------
Please see bz1447918#c17


after fix
----------

    [root@virt-532 ~]# rpm -q pacemaker
    pacemaker-2.1.0-11.el9.x86_64


    [root@virt-532 ~]# pcs status
    Cluster name: STSRHTS12621
    Cluster Summary:
      * Stack: corosync
      * Current DC: virt-532 (version 2.1.0-11.el9-7c3f660707) - partition with quorum
      * Last updated: Wed Sep 15 15:50:58 2021
      * Last change:  Wed Sep 15 15:38:23 2021 by root via cibadmin on virt-532
      * 2 nodes configured
      * 6 resource instances configured

    Node List:
      * Online: [ virt-531 virt-532 ]

    Full List of Resources:
      * fence-virt-531	(stonith:fence_xvm):	 Started virt-531
      * fence-virt-532	(stonith:fence_xvm):	 Started virt-532
      * Container bundle set: test-bundle [redis:test]:
        * test-bundle-podman-0 (127.0.0.2)	(ocf:heartbeat:podman):	 Started virt-531
        * test-bundle-podman-1 (127.0.0.3)	(ocf:heartbeat:podman):	 Started virt-532

    Daemon Status:
      corosync: active/disabled
      pacemaker: active/disabled
      pcsd: active/enabled

    [root@virt-532 ~]# crm_resource --force-start --resource test-bundle
    Sorry, the force-start option doesn't support bundled resources
    crm_resource: Error performing operation: Unimplemented

    [root@virt-532 ~]# crm_resource --force-stop --resource test-bundle
    Sorry, the force-stop option doesn't support bundled resources
    crm_resource: Error performing operation: Unimplemented

    [root@virt-532 ~]# crm_resource --force-promote --resource test-bundle
    Sorry, the force-promote option doesn't support bundled resources
    crm_resource: Error performing operation: Unimplemented

    [root@virt-532 ~]# crm_resource --force-demote --resource test-bundle
    Sorry, the force-demote option doesn't support bundled resources
    crm_resource: Error performing operation: Unimplemented

    [root@virt-532 ~]# crm_resource --force-check --resource test-bundle
    Sorry, the force-check option doesn't support bundled resources
    crm_resource: Error performing operation: Unimplemented


    [root@virt-532 ~]# pcs resource debug-start test-bundle
    Error: unable to debug-start a bundle

    [root@virt-532 ~]# pcs resource debug-stop test-bundle
    Error: unable to debug-stop a bundle

    [root@virt-532 ~]# pcs resource debug-promote test-bundle
    Error: unable to debug-promote a bundle

    [root@virt-532 ~]# pcs resource debug-demote test-bundle
    Error: unable to debug-demote a bundle

    [root@virt-532 ~]# pcs resource debug-monitor test-bundle
    Error: unable to debug-monitor a bundle

When using crm_resource --force-start ...etc. command on bundles we get an error message that bundled resources are not supported.

Marking verified in pacemaker-2.1.0-11.el9