Bug 854202
Summary: | Upgrade-Temp admins not removed after upgrade | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | Rehana <redakkan> |
Component: | aeolus-configure | Assignee: | Steve Linabery <slinaber> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Giulio Fidente <gfidente> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.1.0 | CC: | dajohnso, gfidente, jlaska, morazi |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | aeolus-configure-2.8.8-1.el6cf | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-12 15:17:53 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
Rehana
2012-09-04 10:51:22 UTC
I can't reproduce this. I did the following 5 times and only see one administrator account using rails console afterwards: aeolus-cleanup; aeolus-cleanup; yum -y remove aeolus-* rubygem-aeolus-* yum -y install aeolus-all aeolus-conductor-devel && \ aeolus-configure -p mock && \ yum --enablerepo=aeolus-nightly -y update && /usr/share/aeolus-conductor/script/aeolus-upgrade -a -y && \ aeolus-restart-services I tried to reproduce this on fedora17 (as fedora18 is now already in alpha state) The builds I get installed on fedora17 are the following: aeolus-conductor-0.10.4-1.fc17.noarch rubygem-aeolus-cli-0.5.0-1.fc17.noarch aeolus-conductor-daemons-0.10.4-1.fc17.noarch aeolus-all-0.10.4-1.fc17.noarch rubygem-aeolus-image-0.5.0-1.fc17.noarch aeolus-conductor-doc-0.10.4-1.fc17.noarch aeolus-configure-2.6.1-1.fc17.noarch Which repo should I use to upgrade these packages and try to reproduce the bug? please use "aeolus1_1.repo" of upstream aeolus to upgrade. as per Dave's suggestion, this is not happening on RHEL using aeolus-configure-2.8.8-1.el6cf so I'm moving the bug to VERIFIED state. if the problem is still happening on Fedora, it should be reported against the Fedora component aeolus-configure, not the Cloud Engine product from Red Hat CloudForms-1.1 shipped with aeolus-conductor-0.13.24-1.el6cf, aeolus-configure- 2.8.11-1.el6cf, imagefactory-1.0.2-1.el6cf, iwhd-1.5-2.el6, and oz-0.8.0-6.el6cf Marking this bug CLOSED CURRENTRELEASE. Please reopen if the problem has not been addressed in the 1.1 product. If the problem remains, please file packaging bugs using Fedora + conductor against Fedora. |