Bug 1422667
Summary: | cli: specifying seconds as 'n' in 'cib-push --wait=n' command produces TypeError | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Radek Steiger <rsteiger> | ||||
Component: | pcs | Assignee: | Ivan Devat <idevat> | ||||
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.3 | CC: | cfeist, cluster-maint, idevat, omular, tojeline, vlad.socaciu | ||||
Target Milestone: | rc | Keywords: | EasyFix, TestBlocker | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | pcs-0.9.158-2.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-08-01 18:26:07 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: | |||||||
Attachments: |
|
Description
Radek Steiger
2017-02-15 19:49:53 UTC
*** Bug 1441447 has been marked as a duplicate of this bug. *** Support for --wait in the cib-push command has been added in pcs 0.9.152 and the bug was introduced in the very same patch. Therefore this is not a regression. Before pcs 0.9.152 the --wait flag was completely ignored in the cib-push command. Partial workaround is to not specify seconds in the --wait option, i.e.: pcs cluster cib-push cib.xml --wait (In reply to Tomas Jelinek from comment #4) > Partial workaround is to not specify seconds in the --wait option, i.e.: > pcs cluster cib-push cib.xml --wait This does not apply to bug 1441447. In that case, we do not use anywhere the --wait argument. It is probably used internally by some of the pcs commands we are invoking. Evidently, we cannot modify those commands. For us, there is no "EasyFix" to this problem. Would it be possible that we obtain a pcs version prior to 0.9.152-10.el7_3.3? (In reply to vlad.socaciu from comment #5) In the script "activate_cluster_resources_rh7.sh" that is pushed into bug 1441447 there is the line: > pcs cluster cib-push /tmp/pcs-config-$$ --config --wait=300 Here is `pcs cluster cib-push` used with the flag `--wait` which causes the crash. (In reply to Ivan Devat from comment #6) > (In reply to vlad.socaciu from comment #5) > In the script "activate_cluster_resources_rh7.sh" that is pushed into bug > 1441447 there is the line: > > > pcs cluster cib-push /tmp/pcs-config-$$ --config --wait=300 > > Here is `pcs cluster cib-push` used with the flag `--wait` which causes the > crash. Gee, sorry gentlemen, I hadn't noticed that. The --wait parameter was inadvertently added there; I did not even know that it applied to the `pcs cluster cib-push` command. Thank you for pointing this out. Created attachment 1276378 [details]
proposed fix
After fix: [root@rh73-node1:~]# pcs cluster cib > cib.xml [root@rh73-node1:~]# pcs -f cib.xml resource create dummy ocf:pacemaker:Dummy [root@rh73-node1:~]# pcs cluster cib-push cib.xml --wait=10 CIB updated [root@rh73-node1:~]# echo $? 0 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, 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/RHBA-2017:1958 |