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.