Bug 858782
| Summary: | aeolus-upgrade fails when upgrading from 1.0.1 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Giulio Fidente <gfidente> | ||||||
| Component: | aeolus-conductor | Assignee: | Scott Seago <sseago> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Giulio Fidente <gfidente> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 1.1.0 | CC: | asettle, dajohnso, dmacpher, lbrindle, morazi, sseago | ||||||
| Target Milestone: | beta2 | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | aeolus-conductor-0.13.14-1.el6cf | Doc Type: | Bug Fix | ||||||
| Doc Text: |
On Red Hat Enterprise Linux 6.3 systems, upgrades from CloudForms 1.0.1 to 1.1 failed with the error:
"Migrate aeolus-conductor rails database FAILED"
Upgrade mechanism using user object hooks to create entities caused this error. This update fixes this behavior and the upgrade now works as expected.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-12-04 15:20:40 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 614472 [details]
aeolus_upgrade.log
Patch on list: [PATCH conductor] bug 858782: don't rely on User object hooks to create entities Pushed to master and 1.1: master: 5f5761caaeef52818fda5603228817ea268ba9ac 1.1: 6b501f4b55d5c76cc47bde71088d21ca5cf3bdda works with aeolus-conductor-0.13.14-1.el6cf 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/RHEA-2012-1516.html |
Created attachment 614469 [details] console session log Description of problem: aeolus-upgrade fails when upgrading from 1.0.1 on rhel6.3 Version-Release number of selected component (if applicable): aeolus-conductor-0.13.8-1.el6cf Steps to Reproduce: 1. install v1.0.1 which includes aeolus-conductor-0.8.34-1.el6cf 2. update via yum to aeolus-conductor-0.13.8-1.el6cf 3. launch aeolus-services stop 4. launch /usr/share/aeolus-conductor/script/aeolus-upgrade Actual results: [root@qeblade22 ~]# /usr/share/aeolus-conductor/script/aeolus-upgrade ================================================================================ Aeolus-conductor upgrade ================================================================================ 1/3: Migrate aeolus-conductor rails database (0001_migrate_conductor_db.sh) Executes rake db:migrate for the aeolus-conductor database Do you want to proceed? (y/n): y Migrate aeolus-conductor rails database FAILED. ================================================================================ Finished 0 of 3 upgrade steps Additional info: session log is attached