Bug 1626934
Summary: | Failed to unset host/host group's openscap_proxy_id with "undefined method `destroy' for nil:NilClass" error | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> |
Component: | SCAP Plugin | Assignee: | Ondřej Pražák <oprazak> |
Status: | CLOSED ERRATA | QA Contact: | Jameer Pathan <jpathan> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.2 | CC: | egolov, jpathan, mhulan, mpusater, oprazak |
Target Milestone: | 6.6.0 | Keywords: | Patch, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-foreman_openscap-0.11.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 19:51:48 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
Hao Chang Yu
2018-09-10 06:50:30 UTC
Created redmine issue http://projects.theforeman.org/issues/24883 from this bug Upstream bug assigned to oprazak Upstream bug assigned to oprazak Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24883 has been resolved. Verified Reproduced with satellite-6.3.5.2-1.el7sat.noarch Verified with: - Satellite 6.6.0 snap 9 - tfm-rubygem-foreman_openscap-1.0.3-1.el7sat.noarch Test steps: 1) Choose a host/host group with OpenSCAP Capsule set. 2) Web UI -> Configure -> Smart Class Parameters -> search for "server" parameter. 3) In server parameter -> Under "Specify matchers" -> remove host/host group which was created earlier. 4) Web UI -> Configure -> Edit host/host group -> Unset OpenSCAP Capsule -> Click submit Observation: - no errors - host/host group updated successfully. 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-2019:3172 |