Bug 1077079
| Summary: | 'engine-backup --mode=restore' fails after engine-cleanup on postgres 8 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED ERRATA | QA Contact: | sefi litmanovich <slitmano> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.0 | CC: | acathrow, adahms, didi, eedri, emesika, gklein, iheim, lpeer, pstehlik, Rhev-m-bugs, sbonazzo, scohen, s.kieske, treydock, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, attempting to run the engine-backup command to restore an engine database after running the engine-cleanup command would fail with an error message indicating that the database was not empty. This was caused by a reference to the procedural language plpgsql still existing in the database. Now, the logic for the engine-backup command has been revised so that this language will be ignored if present, allowing the command to complete successfully.
|
Story Points: | --- |
| Clone Of: | 1069131 | Environment: | |
| Last Closed: | 2014-04-09 17:58:49 UTC | Type: | --- |
| 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: | 1069131 | ||
| Bug Blocks: | |||
|
Comment 3
sefi litmanovich
2014-03-24 15:02:39 UTC
This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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. http://rhn.redhat.com/errata/RHBA-2014-0384.html Closing old needinfo's. |