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 1927394 - New web UI - cleanup of resource and fence device doesn't work
Summary: New web UI - cleanup of resource and fence device doesn't work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.5
Assignee: Ivan Devat
QA Contact: cluster-qe@redhat.com
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks: 1552470 1996067 1999014
TreeView+ depends on / blocked
 
Reported: 2021-02-10 16:24 UTC by Michal Mazourek
Modified: 2021-11-09 19:17 UTC (History)
9 users (show)

Fixed In Version: pcs-0.10.8-2.el8
Doc Type: Bug Fix
Doc Text:
Cause: Web ui uses unsupported flag "force" in resource cleanup request to backend. Consequence: Request fails on backend. Fix: Web ui don't use flag "force" anymore. Result: It is possible to cleanup resource from web ui.
Clone Of:
Environment:
Last Closed: 2021-11-09 17:34:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (903 bytes, patch)
2021-06-10 14:30 UTC, Ivan Devat 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4142 0 None Closed Configuring new physical worker node and add to the OCP cluster. 2022-04-26 18:46:50 UTC

Description Michal Mazourek 2021-02-10 16:24:34 UTC 
Description of problem:
It is not possible to cleanup failed operations from history of the resource and fence agent in the new web UI. 


Version-Release number of selected component (if applicable):
pcs-0.10.8-1.el8


How reproducible:
always


Steps to Reproduce:
- In specific resource page, click 'Cleanup' under the three dots at top right corner and confirm the cleanup (tried on ocf:heartbeat:Dummy)
- The same goes for fence devices


Actual results:
Message appears:
"Danger alert:Communication error while: cleanup resource "resource-1". Details in the browser console."

In console:
Invalid value undefined supplied to : ({ success: "true" } | { error: "true", stdout: string, stderror: string })/0: { success: "true" }/success: "true"
Invalid value [] supplied to : ({ success: "true" } | { error: "true", stdout: string, stderror: string })/1: { error: "true", stdout: string, stderror: string }/stdout: string
Invalid value ["Error: Specified option '--force' is not supported in this command\n"] supplied to : ({ success: "true" } | { error: "true", stdout: string, stderror: string })/1: { error: "true", stdout: string, stderror: string }/stderror: string

This is hinting, that the back end used the cleanup command with --force option, which generates the same error in cli.
[root@virt-058 ~]# pcs resource cleanup r1 --force
Error: Specified option '--force' is not supported in this command
[root@virt-058 ~]# pcs stonith cleanup fence-virt-058 --force
Error: Specified option '--force' is not supported in this command


Expected results:
Cleanup of resources and fence devices works
Comment 2 Ivan Devat 2021-06-10 14:30:04 UTC 
Created attachment 1789876 [details]
proposed fix
Comment 3 Miroslav Lisik 2021-06-14 14:22:08 UTC 
Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-2.el8.x86_64

[root@r8-node-01 ~]# crm_resource --resource d-01 --fail -H r8-node-01
Waiting for 1 reply from the controller
... got reply (done)
[root@r8-node-01 ~]# crm_resource --resource fence-r8-node-01 --fail -H r8-node-01
Waiting for 1 reply from the controller
... got reply (done)
[root@r8-node-01 ~]# pcs resource failcount show
Failcounts for resource 'd-01'
  r8-node-01: 1
Failcounts for resource 'fence-r8-node-01'
  r8-node-01: 1

Web UI:
- In resource detail of d-01 resource we see issues:
Warning alert:Failed to asyncmon d-01 on Fri Jun 11 11:30:30 2021 on node r8-node-01: Simulated failure
Danger alert:Resource failed

- After clicking on Cleanup button, confirmation diallog shows up:
Cleanup resource?
This makes the cluster forget failed operations from history of the resource and re-detects its current state.

- After clicking on "Cleanup button" failure is cleaned.

- In Fence Devices detail of fence-r8-node-01 device we see issues:
Warning alert:Failed to asyncmon fence-r8-node-01 on Fri Jun 11 11:30:39 2021 on node r8-node-01: Simulated failure

- After clicking on Cleanup button, confirmation diallog shows up:
Cleanup fence device?
This makes the cluster forget failed operations from history of the fence device and re-detects its current state.

- After clicking on "Cleanup button" failure is cleaned.

[root@r8-node-01 ~]# pcs resource failcount show
No failcounts
Comment 10 errata-xmlrpc 2021-11-09 17:34:53 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 (Low: pcs security, bug fix, and enhancement update), 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/RHSA-2021:4142
Note You need to log in before you can comment on or make changes to this bug.