Bug 1327984

Summary: [cli] "pcs constraint show" should not produce futile labels
Product: Red Hat Enterprise Linux 9 Reporter: Jan Pokorný [poki] <jpokorny>
Component: pcsAssignee: Ondrej Mular <omular>
Status: CLOSED MIGRATED QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 9.0CC: cfeist, cluster-maint, idevat, mlisik, mpospisi, nhostako, omular, tojeline
Target Milestone: rcKeywords: MigratedToJIRA, Reopened, Triaged
Target Release: 9.4Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 18:16:47 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:
Embargoed:

Description Jan Pokorný [poki] 2016-04-18 08:13:09 UTC
For instance see
http://oss.clusterlabs.org/pipermail/users/2016-April/002666.html

For posterity, quoting a relevant part:
> # pcs constraint show --full
> Location Constraints:
>   Resource: IPService
>     Enabled on: nodo1 (score:10) (id:location-IPService-nodo1-10)
>     Enabled on: nodo2 (score:9) (id:location-IPService-nodo2-9)
>     Enabled on: nodo1 (score:INFINITY) (role: Started) (id:cli-prefer-IPService)
> [...]
> Ordering Constraints:
> Colocation Constraints:
>   Web with IPService (score:INFINITY) (id:colocation-Web-IPService-INFINITY)
>   MTA with IPService (score:INFINITY) (id:colocation-MTA-IPService-INFINITY)
>   clusterdataClone with IPService (score:INFINITY) (rsc-role:Master)
> (with-rsc-role:Started)
> (id:colocation-clusterdataClone-IPService-INFINITY)

Emitting "Ordering Constraints" in this case has no meaning whatsoever,
it only clutters the output for others (at least the command originator)
to evaluate mentally as a spam.

Please, make pcs outputs as concise (spam-free) as possible to avoid
the needless mental strain.

I wouldn't worry about possible scripts relying on pcs output in this
case too much: you need a FSM only acting upon observing
> Ordering Constraints:
line, and when this won't show up, there is nothing to process in effect.

Comment 4 RHEL Program Management 2020-12-15 07:41:02 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 7 RHEL Program Management 2023-09-22 18:15:39 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 RHEL Program Management 2023-09-22 18:16:47 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.