Bug 1250277 - certification 0 in status line
certification 0 in status line
Status: NEW
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Greg Nichols
rhcert qe
Depends On:
  Show dependency treegraph
Reported: 2015-08-04 20:58 EDT by Brian Brock
Modified: 2018-03-22 16:36 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Brock 2015-08-04 20:58:30 EDT
The certification linked on the status line after starting a test (fv_*) is listed as "certification 0".  The actual certification number is 3, with only other certs being 1 and 2.

RHEL 7.1 LTS is running:

RHEL 6.7 SUT is running:

Happens consistently with one cert on one system, status line is always "certification 0".  Looking for other patterns, will add them.

Steps to Reproduce:
1. Install an LTS and SUT, both running the server & listener
2. Create a cert, add the SUT to it
3. watch the status line

Actual results:

Status	Testing
ready for certification 0	(busy)

The link for certification 0 is http://$LTS/certification?id=0&type=

That page contains (as its entire content section below the nav bar):
Error: rpath or id not specified

Expected results:
link to the actual certification, certification 3.

Additional info:
LTS had 3 hardware certs. The other certs each have more than one system, but are for other certifying releases.  This cert has only this system.  It last ran on 7-29, before updating redhat-certification-hardware.  Since then I've run tests from the command line twice (fv_* runs).  Results for previous test run appear normal, but there's nothing in the logs from  the current run.

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