Bug 1249570 - rhcert should check if the rhcert.xml.gz file created is valid or not before sending it to CWE
Summary: rhcert should check if the rhcert.xml.gz file created is valid or not before ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: rhcert qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-03 10:31 UTC by Anshul Behl
Modified: 2018-04-26 05:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-26 05:14:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anshul Behl 2015-08-03 10:31:32 UTC
Description of problem:

Currently, there are no checks in rhcert to see if the rhcert.xml.gz file is valid or not. 

Actual results:
Results are forwarded to CWE


Expected results:
File if not valid should not be submitted to CWE

http://file.pnq.redhat.com/abehl/rhcert-results-rhel7-41-171.englab.brocade.com-20150727095809.xml.gz is an invalid file which was submitted and caused failures in CWE side.

Comment 1 Greg Nichols 2015-08-03 13:31:06 UTC
What is invalid with the above file?   What validity checks would you like rhcert to add?

Comment 2 Anshul Behl 2015-08-03 13:55:10 UTC
This file does not have the attachment tag which contains the encoded base64 content which in turn can be decoded to create the original attachment itself.
I am not sure what resulted in the formation of such file, but we can make rules like if attachment tag is not present for a file it is invalid.

Comment 3 Greg Nichols 2015-08-03 14:15:00 UTC
So the real problem is the attachments are missing, correct?

Comment 4 Anshul Behl 2015-08-03 14:17:56 UTC
Yes, that is right and we can maybe catch the same thing on rhcert side or on CWE, partner should be informed saying that the file is not valid.


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