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.
Description of problem:
The hint for location config shows the possibility of using regex. At first glance this hint makes it look like it is possible to filter the resource using `regexp%str`. It is not clear that this only shows the location constraints for the regex (even if it is under the `resources` argument)
Version-Release number of selected component (if applicable):
[root@virt-031 ~]# pcs --version
0.10.14
Steps to Reproduce:
[root@virt-031 ~]# pcs constraint location config --help
...
location [config | show [resources [<resource>...]] | [nodes [<node>...]]]
[--all] [--full]
List all the current location constraints that are not expired. If
'resources' is specified, location constraints are displayed per
resource (default). If 'nodes' is specified, location constraints are
displayed per node. If specific nodes or resources are specified then
we only show information about them. Resource may be either a resource
id <resource_id> or %<resource_id> or resource%<resource_id>, or a
resource name regular expression regexp%<resource_pattern>. If --full
is specified show the internal constraint id's. If --all is
specified show the expired constraints.
...
Actual results:
It is not clear from the hint and argument that they do not filter the resource location constraints using the regex, but only show the location constraints created for the regex.
Expected results:
The option to display Location constraints created for regex should be under another argument (`regexes`), or it should be clear from the tooltip how the option is used.
DevTestResults:
[root@r09-03-b ~]# pcs constraint location config --help
location [config [resources [<resource reference>...]] | [nodes [<node>...]]]
[--all] [--full] [--output-format text|cmd|json]
List all the current location constraints that are not expired. If
'resources' is specified, location constraints are displayed per
resource. If 'nodes' is specified, location constraints are displayed
per node. If specific nodes, resources or resource name regular
expressions are specified, only constraints containing those will be
shown. Resource reference may be either a resource id <resource_id> or
%<resource_id> or resource%<resource_id>, or a resource name regular
expression regexp%<resource_pattern>. If --full is specified show the
internal constraint id's. If --all is specified show the expired
constraints.
There are 3 formats of output available: 'cmd', 'json' and 'text',
default is 'text'. Format 'text' is a human friendly output. Format
'cmd' prints pcs commands which can be used to recreate the same
configuration. Format 'json' is a machine oriented output of the
configuration.
The help text is updated.
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-2023:6316
Comment 11Red Hat Bugzilla
2024-03-07 04:25:27 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: The hint for location config shows the possibility of using regex. At first glance this hint makes it look like it is possible to filter the resource using `regexp%str`. It is not clear that this only shows the location constraints for the regex (even if it is under the `resources` argument) Version-Release number of selected component (if applicable): [root@virt-031 ~]# pcs --version 0.10.14 Steps to Reproduce: [root@virt-031 ~]# pcs constraint location config --help ... location [config | show [resources [<resource>...]] | [nodes [<node>...]]] [--all] [--full] List all the current location constraints that are not expired. If 'resources' is specified, location constraints are displayed per resource (default). If 'nodes' is specified, location constraints are displayed per node. If specific nodes or resources are specified then we only show information about them. Resource may be either a resource id <resource_id> or %<resource_id> or resource%<resource_id>, or a resource name regular expression regexp%<resource_pattern>. If --full is specified show the internal constraint id's. If --all is specified show the expired constraints. ... Actual results: It is not clear from the hint and argument that they do not filter the resource location constraints using the regex, but only show the location constraints created for the regex. Expected results: The option to display Location constraints created for regex should be under another argument (`regexes`), or it should be clear from the tooltip how the option is used.