Bug 1662991
| Summary: | [RFE] Database restore should not start when evmserverd is running | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Matouš Mojžíš <mmojzis> |
| Component: | Appliance | Assignee: | Yuri Rudman <yrudman> |
| Status: | CLOSED ERRATA | QA Contact: | Matouš Mojžíš <mmojzis> |
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | medium | ||
| Version: | 5.10.0 | CC: | abellott, dmetzger, jhenner, obarenbo, simaishi, yrudman |
| Target Milestone: | GA | Keywords: | FutureFeature |
| Target Release: | 5.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | backup:appliance:console | ||
| Fixed In Version: | 5.11.0.8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-12-12 13:34:59 UTC | Type: | Bug |
| 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: | |||
|
Description
Matouš Mojžíš
2019-01-02 16:38:04 UTC
New commit detected on ManageIQ/manageiq-appliance_console/master: https://github.com/ManageIQ/manageiq-appliance_console/commit/21d7476d86348a3755f9aa405c01550a3d017b8b commit 21d7476d86348a3755f9aa405c01550a3d017b8b Author: Yuri Rudman <yrudman> AuthorDate: Mon May 20 15:05:55 2019 -0400 Commit: Yuri Rudman <yrudman> CommitDate: Mon May 20 15:05:55 2019 -0400 do not attempt to restore db if evmserverd is running https://bugzilla.redhat.com/show_bug.cgi?id=1662991 lib/manageiq/appliance_console/database_admin.rb | 5 + spec/database_admin_spec.rb | 11 +- 2 files changed, 15 insertions(+), 1 deletion(-) Verified in 5.11.0.13. I am not able to restore database when evmserverd server is running. *** Bug 1731185 has been marked as a duplicate of this bug. *** 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/RHBA-2019:4199 |