aboutsummaryrefslogtreecommitdiffstats
path: root/puppet/services/README.rst
diff options
context:
space:
mode:
authorSofer Athlan-Guyot <sathlang@redhat.com>2017-02-24 17:01:35 +0100
committerSofer Athlan-Guyot <sathlang@redhat.com>2017-02-24 22:50:51 +0100
commit577ea9b01fb62c7f59f7e47b1f9959c52163ce08 (patch)
tree2eee1f4a56aac4b491bc42235abf9b4f3fc84573 /puppet/services/README.rst
parentea61f7918c723914374c57fc6e87e192fdeb6f7e (diff)
Upgrade nova-api/scheduler/conductor packages at step3 not step2.
The nova-api, nova-scheduler nova-conductor packages are updated during step2. The package upgrade trigger a restart of the service which fails and is constantly retried by systemd: Feb 24 12:34:24 centos-7-2-node-rax-iad-7463943-440549 systemd[1]: Failed to start OpenStack Nova Scheduler Server. Feb 24 12:34:24 centos-7-2-node-rax-iad-7463943-440549 systemd[1]: Unit openstack-nova-scheduler.service entered failed state. Feb 24 12:34:24 centos-7-2-node-rax-iad-7463943-440549 systemd[1]: openstack-nova-scheduler.service failed. Feb 24 12:34:24 centos-7-2-node-rax-iad-7463943-440549 systemd[1]: openstack-nova-scheduler.service holdoff time over, scheduling restart. We eventually reach timeout. We use https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/tripleo-packages.yaml#L44-L46 to upgrade existing packages. Add a note to the README.rst to make people aware of the general upgrade done at step3 and limit its usage to new package for individual service. Change-Id: I13b51bcfe0c98034944613f7e1c3f0168cd4de76 Closes-Bug: #1667728 (cherry picked from commit 5593877817b332bd7a650f051cff5f5988ab1e54)
Diffstat (limited to 'puppet/services/README.rst')
-rw-r--r--puppet/services/README.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/puppet/services/README.rst b/puppet/services/README.rst
index 9c2d8c5c..d9afe602 100644
--- a/puppet/services/README.rst
+++ b/puppet/services/README.rst
@@ -91,7 +91,9 @@ step, "step2" for the second, etc.
2) Stop all control-plane services, ready for upgrade
- 3) Perform a package update, (either specific packages or the whole system)
+ 3) Perform a package update and install new packages: A general
+ upgrade is done, and only new package should go into service
+ ansible tasks.
4) Start services needed for migration tasks (e.g DB)