Bug 1378400
| Summary: | Failed migration task when upgrading from 5.6.2 -> 5.7.0.2 | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | luke couzens <lcouzens> |
| Component: | Documentation | Assignee: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.7.0 | CC: | abellott, adahms, cpelland, dajohnso, dayleparker, fdewaley, hhudgeon, jhardy, jvlcek, ncarboni, obarenbo, simaishi |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | black:upgrade:migration | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-31 00:08:16 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: | 1383147 | ||
|
Comment 3
CFME Bot
2016-09-26 08:26:34 UTC
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f9f4cfcb13ed8219331a3ceb6481ff8bcaf72c56 commit f9f4cfcb13ed8219331a3ceb6481ff8bcaf72c56 Author: Šimon Lukašík <isimluk> AuthorDate: Mon Sep 26 09:27:54 2016 +0200 Commit: Šimon Lukašík <isimluk> CommitDate: Mon Sep 26 09:27:54 2016 +0200 Make sure to publish error msg when saving region replication role https://bugzilla.redhat.com/show_bug.cgi?id=1378400 app/controllers/ops_controller/settings/common.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) This is actually solved by logging out and then logging back in. I don't think we currently have a better way to get around this issue. I'm not sure exactly what is happening, but it has something to do with the new ruby version. Maybe Satoe can give some more detail. After 'yum update', ruby 2.3 will be on the machine, but that's not used yet. But cfme code is expecting rh-ruby23. Also, all the updates that were made to /etc/default/evm or anything that calls aren't used either. Not sure if there is a way to make that happen automatically. (In reply to Nick Carboni from comment #5) > This is actually solved by logging out and then logging back in. I don't > think we currently have a better way to get around this issue. > > I'm not sure exactly what is happening, but it has something to do with the > new ruby version. Maybe Satoe can give some more detail. Based on this comment by Nick Carbon I question whether or not this is be a `Blocker`. If the simple solution is logging out and then logging back in and there is currently no better way to get around this can we consider removing this BZ from the blocker list? (In reply to Nick Carboni from comment #5) > This is actually solved by logging out and then logging back in. I don't > think we currently have a better way to get around this issue. > > I'm not sure exactly what is happening, but it has something to do with the > new ruby version. Maybe Satoe can give some more detail. Based on this comment by Nick Carbon I question whether or not this is be a `Blocker`. If the simple solution is logging out and then logging back in and there is currently no better way to get around this can we consider removing this BZ from the blocker list? The "solution" of logging out and logging in before the db:migrate step is in the latest draft of the upgrade document (being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1383147) I'm going to resolve this with that solution and if we want to spend more time trying to find a better solution we can do that as a separate BZ *** Bug 1414815 has been marked as a duplicate of this bug. *** This content is live on the Customer Portal. Closing. |