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.
Cause:
Web ui calls bad backend url when new resource in a group/as a clone is created.
Consequence:
Creation resource in a group/as a clone is not possible from web ui.
Fix:
Web ui calls correct backend url when new resource in a group/as a clone is created.
Result:
It is possible to create resource in a group/as a clone.
DescriptionMichal Mazourek
2021-02-10 16:05:25 UTC
Description of problem:
In a new resource wizard for creating new resources, there is a step "Settings", where you can specify, if the created resource should be part of a group, cloned or disabled at start. The group and clone (promotable included) options don't take effect.
Version-Release number of selected component (if applicable):
pcs-0.10.8-1.el8
How reproducible:
always
Steps to Reproduce:
- Click 'Create Resource' in 'Resources' tab in new web UI
- In step 3 "Settings", tick either 'Clone' or 'Promotable' or 'Use group' (either with 'Select existing group' or 'Create new group')
- In review step, there is correct information about the entered settings, e.g.:
Group existing group: g1
- Create the resource (tried on ocf:heartbeat:Dummy resource type)
Actual results:
Resource is created without any problems, but the desired setting is not in effect. The problem is with the following 4 cases:
1. Resource is not cloned if 'Clone' option was ticked
2. Resource is nor promotable or clone, if 'Promotable' option was ticked
3. Resource is not in already existing group, if 'Use group' with 'Select existing group' is selected
4. Resource is not in newly created group, if 'Use group' with 'Create new group' is selected
Expected results:
The settings options take effect
Additional info:
Also, creating group via 'Create group' is not possible with just one resource (it is created without problems with multiple resources), which doesn't seem like desired behavior, since it is possible to create group with one resource in cli.
Test:
[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-2.el8.x86_64
Results:
Following settings in 'Create Resource' wizard works:
* Clone
* Clone Promotable
* Group
* Select existing group
* Create new group
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