Bug 1728270
| Summary: | appliance_console: After configuring the "Logfile Configuration" and then running "Harden Appliance Using SCAP Configuration", the old filesystem is not removed from fstab | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Appliance | Assignee: | Brandon Dunne <bdunne> |
| Status: | CLOSED ERRATA | QA Contact: | Md Nadeem <mnadeem> |
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | medium | ||
| Version: | 5.10.5 | CC: | abellott, dmetzger, nansari, obarenbo, rchincho, yrudman |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.10.8 | Flags: | mfeifer:
mirror-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.10.8.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1720223 | Environment: | |
| Last Closed: | 2019-08-13 08:35:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1720223 | ||
| Bug Blocks: | |||
|
Comment 2
CFME Bot
2019-07-09 21:23:10 UTC
New commit detected on ManageIQ/manageiq-appliance/hammer: https://github.com/ManageIQ/manageiq-appliance/commit/c2d302c10bfdf40ca2b2c0821f0576ba2995fa0f commit c2d302c10bfdf40ca2b2c0821f0576ba2995fa0f Author: Brandon Dunne <brandondunne> AuthorDate: Mon Jul 8 18:21:32 2019 -0400 Commit: Brandon Dunne <brandondunne> CommitDate: Mon Jul 8 18:21:32 2019 -0400 Update dependency on manageiq-appliance_console Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1728270 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1728403 manageiq-appliance-dependencies.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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:2466 |