OpenStack upgrades - Document subordinate upgrade handling
Bug #1876576 reported by
Ryan Farrell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Charms Deployment Guide |
Fix Released
|
Medium
|
Peter Matulis | ||
Bug Description
It should be more clearly noted somewhere that upgrading a primary application will also upgrade the subordinates associated with it in a deployment.
- [X] This is a doc addition request.
If you have a troubleshooting or support issue, use the following resources:
- Ask OpenStack: https:/
- The mailing list: https:/
- IRC: 'openstack' channel on Freenode
-------
Release: on 2020-04-29 16:09:06
SHA: f1811e69f551b35
Source: https:/
URL: https:/
Revision history for this message
| Peter Matulis (petermatulis) wrote | #1 |
| Changed in charm-deployment-guide: | |
| status: | New → Incomplete |
| Changed in charm-deployment-guide: | |
| assignee: | nobody → Peter Matulis (petermatulis) |
| importance: | Undecided → Medium |
| status: | Incomplete → In Progress |
Revision history for this message
| Peter Matulis (petermatulis) wrote | #2 |
| Changed in charm-deployment-guide: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Thank you for very much for this report. Although the title of the page is "OpenStack upgrades" the page also covers the subject of "Charm upgrades". So I just want to be sure which subject this bug is about. Can you give more detail?