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 - --force-start, --force-stop, --force-monitor etc. with bundles
Summary: --force-start, --force-stop, --force-monitor etc. with bundles
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: 9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 9.0 Beta
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1447918
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-16 19:40 UTC by Ken Gaillot
Modified: 2024-03-08 12:40 UTC (History)
5 users (show)

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
Clone Of: 1447918
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version: 2.1.1
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Cluster Labs 5442 0 None None None 2021-07-16 19:40:39 UTC

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
Note You need to log in before you can comment on or make changes to this bug.