OpenStack upgrade ordering needs better guidance in Appendix B
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charms Deployment Guide |
Fix Released
|
High
|
Peter Matulis |
Bug Description
This page in the charm deployment guide needs better guidance on upgrade order: https:/
There is service-specific guidance at the following that should be accounted for: https:/
The service-specific guidance above should be evaluated to determine any ordering changes.
It says:
"In terms of the upgrade order, begin with ‘keystone’. After that, the rest of the charms can be upgraded in any order."
It also has nova-compute and neutron-gateway listed as a 3 in the "Upgrade order" table.
For example, if nova-compute (ovs agent) is upgraded before neutron-gateway, the client side ovo version could be upgraded before the server side, causing a failure similar to the following: https:/
Note that upgrade ^ from 14.0.0 to 14.0.3 was an unattended upgrade where the operator upgraded packages on the machine and the charm wasn't involved, but it is an example of a network outage caused by upgrading in the wrong order.
description: | updated |
description: | updated |
description: | updated |
summary: |
- Appendix B: OpenStack Upgrades in charm-deployment-guide + upgrade ordering needs better guidance in Appendix B: OpenStack Upgrades + in charm-deployment-guide |
tags: | added: sts |
summary: |
- upgrade ordering needs better guidance in Appendix B: OpenStack Upgrades - in charm-deployment-guide + OpenStack upgrade ordering needs better guidance in Appendix B |
description: | updated |
Changed in charm-deployment-guide: | |
importance: | Undecided → High |
assignee: | nobody → Peter Matulis (petermatulis) |
Important to note that when upgrading services landed on the same metal (such as nova-compute and ceph-osd) that unattended upgrades are disabled until both services have completed their source/ openstack- origin updates.