Bug 1196715
Summary: | Need to remove the 'Default XCCDF Profile' profile from dropdown as it's a blank profile | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kedar Bidarkar <kbidarka> |
Component: | WebUI | Assignee: | Šimon Lukašík <slukasik> |
WebUI sub component: | Foreman | QA Contact: | Kedar Bidarkar <kbidarka> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | cwelton, jmontleo, szadok |
Version: | 6.1.0 | ||
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 05:27:43 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1047797 |
Description
Kedar Bidarkar
2015-02-26 15:12:14 UTC
Proposed fix in upstream: https://github.com/OpenSCAP/foreman_openscap/pull/84 Proposed fix: https://github.com/OpenSCAP/scaptimony/pull/21, @slukasik, please review Please cherry-pick following commits to rubygem-SCAPtimony https://github.com/OpenSCAP/scaptimony/commit/a833d0f5e0622398f251866266b46f776e3b5bf2 https://github.com/OpenSCAP/scaptimony/commit/c1cef82c15fb7f6e0c3a591c90f10910a88ace61 Fixed in maitenance release of scaptimony: 0.3.1 Kedar, thanks for report! Please note however that fix is different from what you have advised. Empty (no profile) is 'Default XCCDF Profile' is defined by SCAP standard and we should support it. However, we have fixed broken guide for 'Default XCCDF Profile'. Clicking on 'show guide' for 'Default XCCDF Profile' now shows the guide. VERIFIED sat6.1 beta snap5. This bug is slated to be released with Satellite 6.1. 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-2015:1592 |