Bug 1207378 - rhcert-backend traceback on TypeError when asked for certification during plan
Summary: rhcert-backend traceback on TypeError when asked for certification during plan
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: Brian Brock
URL:
Whiteboard:
: 1207375 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-30 19:08 UTC by Brian Brock
Modified: 2016-02-16 09:32 UTC (History)
2 users (show)

Fixed In Version: redhat-certification-2.1-20151204
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 09:32:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0196 0 normal SHIPPED_LIVE redhat-certification bug fix and enhancement update 2016-02-16 14:32:09 UTC

Description Brian Brock 2015-03-30 19:08:33 UTC
Description of problem:
rhcert-backend certification can encounter a TypeError with traceback during execution of the 'plan' command.

Version-Release number of selected component (if applicable):
redhat-certification-1.0-20150325.el7

How reproducible:


Steps to Reproduce:
1. start `rhcert-backend plan`
2. state that the system is being used for certification
3. press <enter> for each of the following questions.

Actual results:
traceback on TypeError after 'What certification is this system being tested for?' when blank answer is given.

Also note that the prompt in question ends with '?' not '? ' (no trailing space).

Expected results:
rhcert-backend survives the error.  Prompting again whether this is for certification or similar would be helpful.

Additional info:
# rhcert-backend plan
Verifying test plan
Warning: default plan called
Hardware: LENOVO 4384BN5 4384BN5
OS: Maipo 7.1

Please verify the hardware product information:
    Vendor:
    Make:
    Model:
    Product URL:
    Specification URL:
    Support URL:
    category (Desktop/Workstation|Laptop|Component/Peripheral|Server) Server
response: Server

Is this system being tested for certification? (yes|no) yes
response: yes

response: True
Searching...
Red Hat Catalog User Name: 
Password: 
Searching...

done.
Could not find any matching certification
What certification is this system being tested for?Traceback (most recent call last):
  File "/usr/bin/rhcert-backend", line 37, in <module>
    success = rhcertBackend.do(args)
  File "/usr/lib/python2.7/site-packages/rhcert/client/backend.py", line 171, in do
    result = self.commands[self.command]()
  File "/usr/lib/python2.7/site-packages/rhcert/client/harness.py", line 184, in doPlan
    self.doDiscover()
  File "/usr/lib/python2.7/site-packages/rhcert/client/harness.py", line 110, in doDiscover
    self.editCertification()
  File "/usr/lib/python2.7/site-packages/rhcert/client/harness.py", line 1126, in editCertification
    self.catalog.getCertificationID(self.certification)
  File "/usr/lib/python2.7/site-packages/rhcert/catalog.py", line 276, in getCertificationID
    answer = self.ui.prompt("What certification is this system being tested for?", answers)
  File "/usr/lib/python2.7/site-packages/rhcert/testUI.py", line 53, in prompt
    return self.ui.prompt(message, validation, default)
  File "/usr/lib/python2.7/site-packages/rhcert/commandLineUI.py", line 51, in prompt
    error = validation(response.strip())
TypeError: 'list' object is not callable

Comment 1 Brian Brock 2015-03-30 19:08:59 UTC
*** Bug 1207375 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2016-02-16 09:32:38 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.

https://rhn.redhat.com/errata/RHBA-2016-0196.html


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