Bug 1319559 - Submit cert test log failed
Summary: Submit cert test log failed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: Certification Workflow Engine
Version: 1.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: huanhuan
QA Contact: Suprith Gangawar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 03:34 UTC by rhel-h3c
Modified: 2016-03-23 02:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 02:23:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
error screen (34.06 KB, image/jpeg)
2016-03-21 03:34 UTC, rhel-h3c 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description rhel-h3c 2016-03-21 03:34:19 UTC 
Created attachment 1138401 [details]
error screen

Description of problem:
Submit cert test log failed

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


How reproducible:


Steps to Reproduce:
1.open https://hardware.redhat.com
2.login as vendor
3.click "create" button
4.create new entry: hardware specification
5.fill the info needed and click "continue"
6.in Hardware Verify Specification web, click "yes submit"
7.screen show error: A legal version was not set.

Actual results:


Expected results:


Additional info:
Comment 1 MaoPeng 2016-03-22 00:29:33 UTC 
To reproduce and fix this bug, we need to know more details.
Please tell us if you upload a spec file in the UPLOAD SPECIFICATION section ?
Or you upload a test log file as the title said in that section ?
Comment 2 rhel-h3c 2016-03-22 00:53:13 UTC 
Yes, I upload a spec file in the upload specification section. It's a word file.
I did not upload a test log file, because in this section, I just to create a new entry: hardware specification
Comment 3 Hardware Certification IRC Bot 2016-03-22 02:40:18 UTC 
hi,
I can't reproduce it at locally, and I have tried the following steps:
1. create->"redhat enterprise linux"->select "Hardware Specification" for Entry Type, and fill vendor, make, model and input a file in "Upload Specification" and input description"->continue->"yes submit"
2.create->"redhat enterprise linux"->Keep default"Hardware Specification & Hardware Certification" for Entry Type, and fill vendor, make, model, and keep product, version, platform as default or select "Redhat Enterprise Linux Server for ARM" and select "RHELSA 7.1 DP" and input a file in "Upload Specification" and input description"->continue->"yes submit"

so could you please tell us more details?
1. which Entry Type do you selected?
2. if you selected "Hardware Specification & Hardware Certification", what's the category, product and version do you selected?
or you can tell us all the info you filled to create spec, then we can debug more easily.

Thanks
Comment 4 huanhuan 2016-03-22 02:41:56 UTC 
hi,
I can't reproduce it at locally, and I have tried the following steps:
1. create->"redhat enterprise linux"->select "Hardware Specification" for Entry Type, and fill vendor, make, model and input a file in "Upload Specification" and input description"->continue->"yes submit"
2.create->"redhat enterprise linux"->Keep default"Hardware Specification & Hardware Certification" for Entry Type, and fill vendor, make, model, and keep product, version, platform as default or select "Redhat Enterprise Linux Server for ARM" and select "RHELSA 7.1 DP" and input a file in "Upload Specification" and input description"->continue->"yes submit"

so could you please tell us more details?
1. which Entry Type do you selected?
2. if you selected "Hardware Specification & Hardware Certification", what's the category, product and version do you selected?
or you can tell us all the info you filled to create spec, then we can debug more easily.

Thanks
Comment 5 huanhuan 2016-03-22 05:57:01 UTC 
hi,
I can reproduce it now. We have updated the settings to make it work. You can try again.
Comment 6 rhel-h3c 2016-03-22 11:53:45 UTC 
This issue was fixed, please close it, thanks.
Note You need to log in before you can comment on or make changes to this bug.