Created from redmine issue http://projects.theforeman.org/issues/15171
Upstream bug assigned to ehelms
This is required to support capsule upgrades.
Moving to POST since upstream bug http://projects.theforeman.org/issues/15171 has been closed
Trying to upgrade capsule from snap14.0 to snap14.1 failed for me. ~]# satellite-installer --scenario capsule --upgrade Upgrading... Upgrade Step: stop_services... Upgrade Step: start_databases... Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... Upgrade Step: fix_pulp_httpd_conf... Upgrade Step: start_httpd... Upgrade step start_httpd failed. Check logs for more information. ------------------------------------------------------------------------- [ERROR 2016-06-03 05:59:51 main] Redirecting to /bin/systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. Some services failed to start: httpd [ERROR 2016-06-03 05:59:51 main] Upgrade step start_httpd failed. Check logs for more information. [DEBUG 2016-06-03 05:59:51 main] Exit with status code: 1 (signal was 1) [ERROR 2016-06-03 05:59:51 main] Errors encountered during run: [ERROR 2016-06-03 05:59:51 main] Redirecting to /bin/systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. Some services failed to start: httpd [ERROR 2016-06-03 05:59:51 main] Upgrade step start_httpd failed. Check logs for more information. ------------------------------------------------------------------------ ~]# rpm -qav | grep -i httpd httpd-manual-2.4.6-40.el7_2.1.noarch httpd-2.4.6-40.el7_2.1.x86_64 httpd-tools-2.4.6-40.el7_2.1.x86_64 My Capsule's BaseOS was not upto date earlier and BaseOS packages got updated along with it, while running "yum update" for updating capsule. Could this be an issue? ------------------------------------------------------------------------ Will be attaching foreman-debug shortly.
What seems to work for me to get past this issue is: a) Run "satellite-installer" b) Run "Satellite-installer --scenario capsule --upgrade" Capsule Upgrade worked successfully.
Kedar, Can you try testing this again with 15.1? I have not hit this issue, and I've done many upgrades from 6.1.9 recently.
I don't see this issue while upgrading capsule from sat6.1.9 -> sat6.2 snap15.1 Upgrading... Upgrade Step: stop_services... Upgrade Step: start_databases... Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... Upgrade Step: fix_pulp_httpd_conf... Upgrade Step: start_httpd... Upgrade Step: start_qpidd... Upgrade Step: start_pulp... Upgrade Step: remove_nodes_importers... Upgrade Step: Running installer... Installing Done [100%] [............................] The full log is at /var/log/foreman-installer/capsule.log Upgrade Step: restart_services... Katello upgrade completed! Leaving this bug as is for Kedar to confirm if he is still facing this while performing upgrade between 6.2 snaps.
VERIFIED. @satellite-capsule-6.2.0-17.0.el6sat.noarch katello-installer-base-3.0.0.46-1.el6sat.noarch Upgrade 6.1.9 -> 6.2.0 Snap17: # satellite-installer --upgrade --certs-tar $(hostname).tar Upgrading... Upgrade Step: stop_services... Upgrade Step: start_databases... Upgrade Step: update_http_conf... Upgrade Step: migrate_pulp... Upgrade Step: fix_pulp_httpd_conf... Upgrade Step: start_httpd... Upgrade Step: start_qpidd... Upgrade Step: start_pulp... Upgrade Step: remove_nodes_importers... Upgrade Step: Running installer... Installing Done [100%] [....................................] The full log is at /var/log/foreman-installer/capsule.log Upgrade Step: restart_services... Katello upgrade completed! >>> start_httpd step succeeded
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/RHBA-2016:1501