Bug 720136

Summary: Crash in crm > configure > template > list
Product: Red Hat Enterprise Linux 6 Reporter: Madison Kelly <mkelly>
Component: pacemakerAssignee: Andrew Beekhof <abeekhof>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: cluster-maint, dejanmm, dgregor, jkortus, snagar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pacemaker-1.1.5-7.el6 Doc Type: Bug Fix
Doc Text:
When using the CRM command line interface, running the "configure", "template", and "list" commands in this particular order caused the crm process to terminate unexpectedly with the following error: NameError: global name 'listconfigs' is not defined With this update, the underlying source code has been modified to address this issue so that CRM no longer crashes.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 16:50:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Madison Kelly 2011-07-10 02:17:08 UTC
Description of problem:

When in the CRM shell, going to configure > template and typing 'list' causes a python crash:

====
[root@an-node01 ~]# crm
crm(live)# configure 
crm(live)configure# template 
crm(live)configure template# list
Traceback (most recent call last):
  File "/usr/sbin/crm", line 45, in <module>
    main.run()
  File "/usr/lib64/python2.6/site-packages/crm/main.py", line 293, in run
    if not parse_line(levels,shlex.split(inp)):
  File "/usr/lib64/python2.6/site-packages/crm/main.py", line 147, in parse_line
    rv = d() # execute the command
  File "/usr/lib64/python2.6/site-packages/crm/main.py", line 146, in <lambda>
    d = lambda: cmd[0](*args)
  File "/usr/lib64/python2.6/site-packages/crm/ui.py", line 631, in list
    multicolumn(listconfigs())
NameError: global name 'listconfigs' is not defined
====

Version-Release number of selected component (if applicable):

pacemaker-1.1.5-5.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. install pacemaker
2. start the crm shell
3. type configure, template, list
  
Actual results:

Python crash

Expected results:

No crash

Additional info:

Comment 2 Andrew Beekhof 2011-07-11 01:43:51 UTC
Seen this one before Dejan?

Comment 3 Dejan Muhamedagic 2011-07-11 08:08:10 UTC
Yes, fixed in (devel):

changeset:   10708:5bdfc629f35a
user:        Dejan Muhamedagic <dejan>
date:        Wed Apr 06 17:12:44 2011 +0200
summary:     Dev: Shell: really fix template list

changeset:   10707:44070d3cbc64
user:        Dejan Muhamedagic <dejan>
date:        Wed Apr 06 16:34:05 2011 +0200
summary:     High: Shell: repair template list command

The changesets were transplanted to the 1.1 branch as well.

Comment 4 Andrew Beekhof 2011-07-12 02:26:26 UTC
Excellent. Thanks!

Comment 12 Jaroslav Kortus 2011-10-13 15:04:31 UTC
(10:00:32) [root@marathon-03:~]$ crm
crm(live)# configure
crm(live)configure# template
crm(live)configure template# list
crm(live)configure template# 

bug seems to be gone.
pacemaker-1.1.6-2.el6.x86_64

Comment 13 Jaromir Hradilek 2011-10-26 09:31:41 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When using the CRM command line interface, running the "configure", "template", and "list" commands in this particular order caused the crm process to terminate unexpectedly with the following error:

    NameError: global name 'listconfigs' is not defined

With this update, the underlying source code has been modified to address this issue so that CRM no longer crashes.

Comment 14 errata-xmlrpc 2011-12-06 16:50:40 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1669.html