Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
The user creates a stonith resource and uses the --wait option in the command.
Consequence:
The resource is created and pcs crashes in waiting for the resource to start.
Fix:
Call the function for waiting for resources to start with correct parameters.
Result:
Pcs creates the stonith resource and waits for it to start.
Description of problem:
The command "pcs stonith create [...] --wait" fails with a traceback (the stonith resource does get created/started correctly):
> # pcs stonith create foo fence_xvm --wait
> Traceback (most recent call last):
> File "/usr/sbin/pcs", line 9, in <module>
> load_entry_point('pcs==0.9.162', 'console_scripts', 'pcs')()
> File "/usr/lib/python2.7/site-packages/pcs/app.py", line 208, in main
> cmd_map[command](argv)
> File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 46, in stonith_cmd
> stonith_create(lib, argv_next, modifiers)
> File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 191, in stonith_create
> **settings
> File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 97, in decorated_run
> return run_with_middleware(run, cli_env, *args, **kwargs)
> File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 19, in run
> return next_in_line(env, *args, **kwargs)
> File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 42, in apply
> result_of_next = next_in_line(env, *args, **kwargs)
> File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 68, in apply
> result_of_next = next_in_line(env, *args, **kwargs)
> File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 87, in run
> lib_call_result = run_library_command(lib_env, *args, **kwargs)
> File "/usr/lib/python2.7/site-packages/pcs/lib/commands/stonith.py", line 75, in create
> resource.common.disable(stonith_element)
> File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__
> self.gen.next()
> File "/usr/lib/python2.7/site-packages/pcs/lib/commands/resource.py", line 47, in resource_environment
> for res_id in wait_for_resource_ids
> TypeError: 'bool' object is not callable
> # echo $?
> 1
> # pcs stonith
> foo (stonith:fence_xvm): Started virt-267
Version-Release number of selected component (if applicable):
pcs-0.9.162-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. "pcs stonith create [...] --wait"
Actual results:
pcs fails with the above traceback, while the fencing resource is correctly created and started
Expected results:
no traceback, wait until stonith resource is created/started
Additional info:
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-2018:0866
Description of problem: The command "pcs stonith create [...] --wait" fails with a traceback (the stonith resource does get created/started correctly): > # pcs stonith create foo fence_xvm --wait > Traceback (most recent call last): > File "/usr/sbin/pcs", line 9, in <module> > load_entry_point('pcs==0.9.162', 'console_scripts', 'pcs')() > File "/usr/lib/python2.7/site-packages/pcs/app.py", line 208, in main > cmd_map[command](argv) > File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 46, in stonith_cmd > stonith_create(lib, argv_next, modifiers) > File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 191, in stonith_create > **settings > File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 97, in decorated_run > return run_with_middleware(run, cli_env, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 19, in run > return next_in_line(env, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 42, in apply > result_of_next = next_in_line(env, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 68, in apply > result_of_next = next_in_line(env, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 87, in run > lib_call_result = run_library_command(lib_env, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/pcs/lib/commands/stonith.py", line 75, in create > resource.common.disable(stonith_element) > File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ > self.gen.next() > File "/usr/lib/python2.7/site-packages/pcs/lib/commands/resource.py", line 47, in resource_environment > for res_id in wait_for_resource_ids > TypeError: 'bool' object is not callable > # echo $? > 1 > # pcs stonith > foo (stonith:fence_xvm): Started virt-267 Version-Release number of selected component (if applicable): pcs-0.9.162-1.el7.x86_64 How reproducible: always Steps to Reproduce: 1. "pcs stonith create [...] --wait" Actual results: pcs fails with the above traceback, while the fencing resource is correctly created and started Expected results: no traceback, wait until stonith resource is created/started Additional info: