aboutsummaryrefslogtreecommitdiffstats
path: root/environments/docker.yaml
diff options
context:
space:
mode:
authorMichele Baldessari <michele@acksyn.org>2016-10-10 21:18:26 +0200
committerMichele Baldessari <michele@acksyn.org>2016-10-10 21:18:26 +0200
commit30a570a7f461a4c4411d9cde67d8de9042952016 (patch)
tree37f14b9706ff13a535fa24fde720aff2a302e205 /environments/docker.yaml
parentf9c48f6d62a8af4aba698f1cc7361329609a2c6f (diff)
Actually start the systemd services in step3 of the major-upgrade step
We have the following function in the upgrade process after we updated the packages and called the db-sync commands: services=$(services_to_migrate) ... for service in $(services); do manage_systemd_service start "${service%%-clone}" check_resource_systemd "${service%%-clone}" started 600 done The above is broken because $services contains a list of services to start, so $(services) will return gibberish and the for loop will never execute anything. One of the symptoms for this is the openstack-nova-compute service not restarting on the compute nodes during the yum -y upgrade. The reason for this is that during the service restart, nova-compute waits for nova-conductor to show up in the rabbitmq queues, which cannot happen since the service was actually never started. Change-Id: I811ff19d7b44a935b2ec5c5e66e5b5191b259eb3 Closes-Bug: #1630580
Diffstat (limited to 'environments/docker.yaml')
0 files changed, 0 insertions, 0 deletions