Red Hat Bugzilla – Bug 1518009
os-collect-config doesn't start at boot on split stack deployments with pre-provisioned servers
Last modified: 2018-05-18 13:04:45 EDT
Description of problem: os-collect-config service doesn't start at boot on split stack deployments Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-6.2.4-1.el7ost.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. Deploy OSP11 with split stack on pre-provisioned nodes 2. Reboot one of the nodes 3. Check os-collect-config service status Actual results: [root@controller-0 stack]# systemctl status os-collect-config ● os-collect-config.service - Collect metadata and run hook commands. Loaded: loaded (/usr/lib/systemd/system/os-collect-config.service; disabled; vendor preset: disabled) Active: inactive (dead) Expected results: os-collect-config service is started after a reboot so subsequent stack updates can be applied. Additional info: Before the node reboot: [root@controller-0 stack]# systemctl status os-collect-config ● os-collect-config.service - Collect metadata and run hook commands. Loaded: loaded (/usr/lib/systemd/system/os-collect-config.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2017-11-27 18:18:57 UTC; 3h 29min ago Main PID: 10945 (os-collect-conf) Memory: 760.9M CGroup: /system.slice/os-collect-config.service └─10945 /usr/bin/python /usr/bin/os-collect-config Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 ----------------------- PROFILING ----------------------- Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Target: migration.d Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Script Seconds Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 --------------------------------------- ---------- Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 Nov 27 18:49:17 controller-0 os-collect-config[10945]: dib-run-parts Mon Nov 27 18:49:17 UTC 2017 --------------------- END PROFILING --------------------- Nov 27 18:49:17 controller-0 os-collect-config[10945]: [2017-11-27 18:49:17,406] (os-refresh-config) [INFO] Completed phase migration After the node reboot: [root@controller-0 stack]# systemctl status os-collect-config ● os-collect-config.service - Collect metadata and run hook commands. Loaded: loaded (/usr/lib/systemd/system/os-collect-config.service; disabled; vendor preset: disabled) Active: inactive (dead)
The workaround for this is to just manually enable it by running 'sudo systemctl enable os-collect-config'
It appears that the upstream patch for the backport also includes some extra items that may have partial upgrade implications. We'll have to cherry-pick just part of it.
According to our records, this should be resolved by openstack-tripleo-heat-templates-6.2.7-2.el7ost. This build is available now.
Verified on puddle 2018-05-03.2
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-2018:1627