Bug 1043420 - Log upload fail via webpage
Summary: Log upload fail via webpage
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Hardware Catalog
Version: FEAT
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: hwcert-catalog
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 09:44 UTC by garrickyang
Modified: 2015-06-04 08:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-04 08:11:49 UTC


Attachments (Terms of Use)
fail page (16.44 KB, image/png)
2013-12-16 09:44 UTC, garrickyang
no flags Details

Description garrickyang 2013-12-16 09:44:22 UTC
Created attachment 837174 [details]
fail page

Description of problem:
login redhat web page using garrickyang
I create two projects for Lenovo thinkserver certification,one RD440, one TD340, but both projects faced with failure to upload result log via website. when upload process conduct, page will turn to "can't display page" and upload process will cease, after check "review", no log uploaded successfully.
And I tried, submit by file(select specification rather than result in Review page), upload process failed, and using bugzilla page: https://bugzilla.redhat.com/show_bug.cgi?id=1030848 to upload log, the same error occurred.
Finally, I send the log to redhat's employee who review log via email.
So, please help look into this issue, whether it is  account issue ,or redhat website issue 

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

N/A
How reproducible:
Login using account: garrickyang
Upload log file in review tab
when uploading, page turn to "can not display"

Steps to Reproduce:
1.Login hardware.redhat.com using account:garrickyang
2.Search project RD440 or TD340
3.Upload log file in review tab
4.Page turn to "can not display" 

Actual results:
log upload fail

Expected results:

log upload successfully
Additional info:


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