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: ASSIGNED --- QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: low    
Version: 9.0CC: cfeist, cluster-maint, idevat, mlisik, mpospisi, omular, tojeline
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: 9.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:41:02 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.