Bug 1238443
| Summary: | Migration: Db:migrate failure when going version 5.2.4 -> 5.4 while uninstalling rubyrep | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Jared Deubel <jdeubel> |
| Component: | Appliance | Assignee: | Keenan Brock <kbrock> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Krocil <jkrocil> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.4.0 | CC: | abellott, gtanzill, jdeubel, jhardy, jocarter, kbrock, mfeifer, obarenbo, snansi |
| Target Milestone: | GA | ||
| Target Release: | 5.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.5.0.1 | Doc Type: | Bug Fix |
| Doc Text: |
Migrating to the previous version of CloudForms Management Engine would fail with a DB:migrate failure error while un-installing rubyrep. This would happen as the replication workers had the VMDB password stored encrypted with the old key. This bug was fixed by ensuring that legacy keys were loaded before un-installing rubyrep, so the task could complete. Migrating to the new version of CloudForms Management Engine now succeeds as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-08 13:21:11 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
Jared Deubel
2015-07-01 21:34:01 UTC
What version was the appliance that was running the upgrade? They upgraded from 5.3 to 5.4. Let me know if you need the minor version. dajo. could you test this along with https://bugzilla.redhat.com/show_bug.cgi?id=1237245 The goal is to be able to migrate from an early 5.2 -> 5.4.x It looks like replication may be the Achilles heel on this one. But I believe that has been solved by the code in this fix. New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/562bfe3407cf8e064ddd43f6d7cc6df721735045 commit 562bfe3407cf8e064ddd43f6d7cc6df721735045 Author: Keenan Brock <kbrock> AuthorDate: Mon Jul 20 15:54:19 2015 -0400 Commit: Keenan Brock <kbrock> CommitDate: Mon Jul 20 17:19:05 2015 -0400 Fix 5.2 -> 5.4 db:migration with replication When migrating from 5.2 to 5.4, the replication workers have the password stored with an old key. This causes the migration to fail. This loads legacy keys so those tasks can complete https://bugzilla.redhat.com/show_bug.cgi?id=1238443 .../20131216214850_fix_replication_on_upgrade_from_version_four.rb | 4 ++-- ...0131216214850_fix_replication_on_upgrade_from_version_four_spec.rb | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) 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:2551 |