Red Hat Bugzilla – Bug 813090
v7 plan fails when the Hardware Catalog Server is not reachable from the SUT
Last modified: 2015-02-08 16:38:01 EST
Created attachment 577835 [details]
Unable install new v7-1.5-18 test kit on RH6.2 and RH6.1
Steps to Reproduce:
3.Type command line v7 plan
Unable to create v7 test plan
Create v7 test plan
[root@SUT-DL380G7 rh6_x64]# v7 plan
found interface for udisks
found device file /dev/sda
found device file /dev/sdb
Please verify the vendor, make, and model:
Model: ProLiant DL380 G7
Hardware: HP ProLiant ProLiant DL380 G7
OS: Santiago 6.1
Traceback (most recent call last):
File "/usr/bin/v7", line 45, in <module>
success = v7.do(args)
File "/usr/share/v7/lib/v7/hardwaretest.py", line 194, in do
result = self.commands[self.command]()
File "/usr/share/v7/lib/v7/hardwaretest.py", line 325, in doPlan
File "/usr/share/v7/lib/v7/hardwaretest.py", line 249, in doDiscover
File "/usr/share/v7/lib/v7/catalog.py", line 53, in getCertificationID
if not self.isReachable():
File "/usr/share/v7/lib/v7/catalog.py", line 47, in isReachable
print "Could not reach catalog server %s" % catalogServer
NameError: global name 'catalogServer' is not defined
[root@SUT-DL380G7 rh6_x64]# ^C
Created attachment 577837 [details]
Created attachment 578078 [details]
catalog.py patch fixing traceback when catalog is unreachable
*** Bug 813213 has been marked as a duplicate of this bug. ***
Are you able to continue after applying the patch in Comment #4?
From my testing the patch works but prompts for a certID where a "0" will get past this prompt (Bug #813405).
(In reply to comment #7)
> chau.nguyen2, akodenkiri,
> Are you able to continue after applying the patch in Comment #4?
> From my testing the patch works but prompts for a certID where a "0" will get
> past this prompt (Bug #813405).
Applying the patch will also cause the info test to fail the v7 validation step. This is expected behavior.
Can you tell me how to apply this patch?. A brief steps will help a lot.
The file to be patched is
Assuming you've saved the attachment to a file catalog.patch, the command to patch it would be:
> patch /usr/share/v7/lib/v7/catalog.py catalog.patch
I have followed your instruction to apply patch and it got applied without any issue.If i enter "v7 plan" i am not getting any crash but it asks us to enter Certification ID.I don't what certification ID has to enter here. There was no instruction to enter Certification ID on v1.4 kit.Is there any new step is required.?
Please find attached "RHEL6_x64_patch.JPG" snapshot for more details
Created attachment 578351 [details]
(In reply to comment #14)
> I have followed your instruction to apply patch and it got applied without any
> issue.If i enter "v7 plan" i am not getting any crash but it asks us to enter
> Certification ID.I don't what certification ID has to enter here. There was no
> instruction to enter Certification ID on v1.4 kit.Is there any new step is
A CertID of "0" will bypass this prompt. This is a bug, and is being tracked ing Bug #813405.
Thanks. I executed the test by providing "0" as Cert ID. Info and Core tests failed for me. FWIW these tests passed with v1.4 kit. Probably you have another bug here.
The info is expected to fail with the patch applied. The self checks will fail since the test has been modified. If you check the logs the only expected fail is the self check, others would be something else.
Core should not be related to this bug or the patch. If you can check the core logs and decide if it looks like a bug. If so it's worth opening a new bug for that.
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.
no tech note needed.
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.