Bug 1492418
Summary: | Download option for scap-content in CLI shows error undefined method `[]' for nil:NilClass | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
Component: | SCAP Plugin | Assignee: | Ondřej Pražák <oprazak> |
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | bbuckingham, ehelms, mhulan, oprazak |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman_openscap 0.7.8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:33:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nikhil Kathole
2017-09-17 09:42:11 UTC
This is reproducible when scap-content is uploaded using CLI without providing --original-filename parameter. # hammer scap-content create --title="abc" --scap-file=ssg-rhel7-ds.xml --organization-ids=1 SCAP content successfully created # hammer scap-content download --title='abc' --path=/var Could not download the SCAP content file: Error: found more than one scap_content Created redmine issue http://projects.theforeman.org/issues/21124 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21124 has been resolved. VERIFIED Version Tested: Satellite-6.3 Snap 18 steps: # hammer scap-content create --title="abc" --scap-file=ssg-rhel6-ds.xml --organization-ids=1 SCAP content successfully created # hammer scap-content download --id=6 --path=/var SCAP content file downloaded, saved to: /var/abc.xml Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336 |