Bug 1591252 - [usage sanity] The expectations about the administered stack should be clear and enforced
Summary: [usage sanity] The expectations about the administered stack should be clear ...
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
Depends On:
Blocks: 1591258
TreeView+ depends on / blocked
Reported: 2018-06-14 11:54 UTC by Jan Pokorný [poki]
Modified: 2019-06-01 17:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1591258 (view as bug list)
Last Closed:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1359057 None NEW [cli] pcs should provide enhanced, stackable, integrity-protecting "pcs cluster cib/cib-push" alternative 2019-08-19 11:03:19 UTC

Internal Links: 1359057

Description Jan Pokorný [poki] 2018-06-14 11:54:30 UTC
With the intentional branch separation regarding the target stack[1],
interchanging said stacks basically amounts to undefined behaviour
(may sometimes appear working fine, until it won't, to the potential
disappointment of the users).

Sketch of possible solution:

1. pacemaker related parts
1a. check whether "pacemakerd" is present on the root-user-like
    $PATH, bail out if not
1b. run pacemakerd --version and parse the first line
    (e.g. Pacemaker 2.0.0-0.1.rc5.fc29), when pacemaker 2+ detected,
    bail out

2. corosync related parts
2a. probably only parsing "corosync -v" is what's needed(?)

The earlier ahead-of-time warning, the better, both in respect to the
pcs usage flow (should be checked as early as with "pcs cluster auth"?)
and regarding the range of possible combinations -- would suggest to
have this combinatoric sanity established as early as in 7.6 if possible.

[1] https://github.com/ClusterLabs/pcs/pull/171#issuecomment-387689432

Comment 1 Jan Pokorný [poki] 2018-06-15 10:21:08 UTC
Note that using a new, systemic shell pipelining approach [bug 1359057]
would alleviate the need to perform redundant target checks like these
within the single compound command.

Note You need to log in before you can comment on or make changes to this bug.