Bug 964582 - hwcert-backend submit fails: RHEL7 Not accepted by the catalog
hwcert-backend submit fails: RHEL7 Not accepted by the catalog
Status: CLOSED EOL
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Hardware Catalog (Show other bugs)
1.7
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: hwcert-catalog
Brian Brock
:
Depends On:
Blocks: 1052374
  Show dependency treegraph
 
Reported: 2013-05-18 23:18 EDT by Brian Brock
Modified: 2015-07-09 05:58 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-09 05:58:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian Brock 2013-05-18 23:18:13 EDT
Description of problem:

'hwcert-backend submit' does not successfully submit results to the server.
hwcert-client-1.7.0-36.el7

happens every run, regardless of options (so far).

Steps to Reproduce:
1. hwcert-backend plan
2. hwcert-backend run -t core
3. hwcert-backend submit
  


Actual results:

$ hwcert-backend submit

Would you like to submit the results to the hardware catalog? (y|n) y
response: y
What certification is this system being tested for? (new|existing|none) new
response: new
Red Hat Catalog User Name: bbrock@redhat.com
response: bbrock@redhat.com
Password: 
Error: could not open a new certification:
    Fault code: 105
    Fault string: The version "7" is not a legal one.





Expected results:

successful submission


Additional info:
I've tested the passwd and it's correct.  ran 'clean', then same steps with the 'save' command.  I ran 'submit' before tests are run, and after core, then run after just the info test.  Before the tests are run, the 'submit' command exits as expected with 1 returned.  Tested on x86_64 and s390x, I'll post if ppc64 fails.
Comment 8 MaoPeng 2015-07-09 05:58:02 EDT
should be fixed now.
Comment 9 MaoPeng 2015-07-09 05:58:22 EDT
should be fixed now.

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