-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix upload_manifest to handle case where manifest.content is not set #13819
Fix upload_manifest to handle case where manifest.content is not set #13819
Conversation
Signed-off-by: Gaurav Talreja <[email protected]>
trigger: test-robottelo |
1 similar comment
trigger: test-robottelo |
trigger: test-robottelo |
…13819) Update upload_manifest to handle case where manifest.content is not set Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 6013181)
…13819) Update upload_manifest to handle case where manifest.content is not set Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 6013181)
…13819) Update upload_manifest to handle case where manifest.content is not set Signed-off-by: Gaurav Talreja <[email protected]> (cherry picked from commit 6013181)
…atelliteQE#13819) Update upload_manifest to handle case where manifest.content is not set Signed-off-by: Gaurav Talreja <[email protected]>
Problem Statement
Currently, there are many intermittent test failures like below where we use
module_sca_manifest_org
are seen in automation runs, where we don't have content property set in manifester object.Solution
Update upload_manifest to handle case where manifest.content is not set, or when manifest.content is None
Local test results: