Red Hat Bugzilla – Bug 1509158
Mater services were not started automatically after reboot hosts for an upgraded non-ha deployed env
Last modified: 2017-11-28 17:21:23 EST
Description of problem: Run upgrade against a non-ha ocp from v3.6 to v3.7, after upgrade successfully, reboot master hosts, master api and controllers service will not started by default after reboot. They should be enabled in systemd. Workaround is to start all master services manually. # systemctl status atomic-openshift-master* ● atomic-openshift-master-api.service - Atomic OpenShift Master API Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master-api.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2017-11-03 02:48:24 EDT; 1h 45min ago Docs: https://github.com/openshift/origin Main PID: 21656 (openshift) Memory: 283.2M .................... ● atomic-openshift-master-controllers.service - Atomic OpenShift Master Controllers Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master-controllers.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2017-11-03 02:48:35 EDT; 1h 45min ago Docs: https://github.com/openshift/origin Main PID: 21925 (openshift) Memory: 105.8M CGroup: /system.slice/atomic-openshift-master-controllers.service └─21925 /usr/bin/openshift start master controllers --config=/etc/origin/master/master-config.yaml --loglevel=5 --listen=https://0.0.0.0:8444 Version-Release number of the following components: openshift-ansible-3.7.0-0.190.0.git.0.129e91a.el7.noarch How reproducible: always Steps to Reproduce: 1. Install non-ha v3.6 ocp 2. Upgrade v3.6 to v3.7 3. Reboot master host Actual results: Mater services were not started automatically Expected results: Master services should be started as a system service by default Additional info: Please attach logs from ansible-playbook with the -vvv flag
PR Created: https://github.com/openshift/openshift-ansible/pull/6005
Verified on openshift-ansible-3.7.0-0.196.0.git.0.27cd7ec.el7.noarch
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/RHSA-2017:3188