Bug 813405

Summary: v7 should not prompt for certification id when hardware catalog is unreachable
Product: [Retired] Red Hat Hardware Certification Program Reporter: Greg Nichols <gnichols>
Component: Test Suite (harness)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.5CC: czhang, gbai, rlandry, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
no tech note needed.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-05 21:37:41 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:
Bug Depends On:    
Bug Blocks: 767775    
Attachments:
Description Flags
catalog.py patch to continue as if "none" is entered when the hardware catalog is unreachable none

Description Greg Nichols 2012-04-17 16:33:48 UTC 
Description of problem:

When the hardware catalog is unreachable, v7 continues assuming there is an existing certification, and prompts for the certification id.  It should assume there is no certification id instead.

The work-around for this bug is to enter 0 (zero) for the certification ID.


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

v7 1.5 R20
Comment 1 Greg Nichols 2012-04-18 14:04:03 UTC 
Created attachment 578364 [details]
catalog.py patch to continue as if "none" is entered when the hardware catalog is unreachable
Comment 5 Caspar Zhang 2012-06-04 08:04:45 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:
no tech note needed.
Comment 7 errata-xmlrpc 2012-06-05 21:37:41 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-2012-0711.html