pausing hacluster no longer needed during series upgrades
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
Fix Released
|
High
|
Peter Matulis |
Bug Description
This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:
- [x] This doc is inaccurate in this way: ______
- [ ] This is a doc addition request.
- [x] I have a fix to the document that I can paste below including example: input and output.
If you have a troubleshooting or support issue, use the following resources:
- The mailing list: https:/
- IRC: 'openstack' channel on OFTC
-------
Release: 0.0.1.dev753 on 2023-08-16 18:30:42
SHA: 74d0eea30bb8e75
Source: https:/
URL: https:/
Commit https:/
Specifically, I think the following sentence should be dropped from https:/
> If hacluster is used, pause the hacluster units not associated with the principal leader machine.
Additionally, I think a note should be added to warn users that HA clusters will be inoperable throughout the upgrade (of a given application); this is a behavior change as it used to be possible to keep the cluster alive by carefully pausing only one unit at a time.
Changed in charm-guide: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in charm-guide: | |
assignee: | nobody → Peter Matulis (petermatulis) |
Fix proposed to branch: master /review. opendev. org/c/openstack /charm- guide/+ /893436
Review: https:/