Created attachment 596176 [details] after_upgrade Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Start a image build to rhevm( image status changed to 'building' :PFA:before_upgrade) 2.Do yum update and excute the upgrade script Actual results: Observed that images status was set back to 'build' (PFA:after_upgrade and the imagefactory.log) I guess this happend may be due to the 'aeolus-services-stop' in the upgrade script. Is it possible to save the running process and start them after update is completed? Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.34-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.3-2.el6_2.noarch aeolus-configure-2.5.10-1.el6cf.noarch aeolus-conductor-daemons-0.8.34-1.el6cf.noarch aeolus-all-0.8.34-1.el6cf.noarch aeolus-conductor-doc-0.8.34-1.el6cf.noarch
Created attachment 596178 [details] before_upgrade
Created attachment 596180 [details] imagefactory.log
My forthcoming patch will mimic the katello-upgrade script behaviour, so that if the upgrade script detects running services, it will complain and not do the upgrade. If, however, the script is called with the --auto-stop option, it will restart services automatically. In this way the user has full control over stopping services that might lose data otherwise.
Currently the script is listing all the running process and informed the user to go with auto-stop option to continue with upgrade,even while have some image upload process. not sure what should be image status "Failed" or "Build" Currently i am unable to check this due to the upgrade bug https://bugzilla.redhat.com/show_bug.cgi?id=860564 Need to retest the same,once the above mentioned bug is fixed
Retested the bug.Observed that the script is listing all the running process and informed the user to go with auto-stop option to continue with upgrade,even while have some image upload process. Observed that the image status is set to "Build", since the first attempt of build is failed, i feel its should show the message "1 build attempt failed" Steve Linabery, Any thoughts ? on rpm -qa | grep aeolus aeolus-conductor-doc-0.13.16-1.el6cf.noarch rubygem-aeolus-cli-0.7.3-1.el6cf.noarch aeolus-all-0.13.16-1.el6cf.noarch aeolus-conductor-0.13.16-1.el6cf.noarch aeolus-configure-2.8.8-1.el6cf.noarch aeolus-conductor-daemons-0.13.16-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch
(In reply to comment #8) > Retested the bug.Observed that the script is listing all the running process > and informed the user to go with auto-stop option to continue with > upgrade,even while have some image upload process. > > Observed that the image status is set to "Build", since the first attempt of > build is failed, i feel its should show the message "1 build attempt failed" > > Steve Linabery, > > Any thoughts ? > > > on > > rpm -qa | grep aeolus > aeolus-conductor-doc-0.13.16-1.el6cf.noarch > rubygem-aeolus-cli-0.7.3-1.el6cf.noarch > aeolus-all-0.13.16-1.el6cf.noarch > aeolus-conductor-0.13.16-1.el6cf.noarch > aeolus-configure-2.8.8-1.el6cf.noarch > aeolus-conductor-daemons-0.13.16-1.el6cf.noarch > rubygem-aeolus-image-0.3.0-12.el6.noarch As we discussed in irc with the other devs, I think this is a documentation issue. Admin should make sure no running builds before doing upgrade. will update with a release note doctype.
Steve, Can you please confirm whether this has been added to Release note or not ? If not then i can move it back to "assigned" status.
another bugzilla has been created, against Documentation, to document such a behaviour