This is an automated email from the ASF dual-hosted git repository.
abhisar pushed a commit to branch 4.20
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/4.20 by this push:
new 9a954f84 upgrade guard explanation (#609)
9a954f84 is described below
commit 9a954f84a1ce3d9fcfb28a5aa11ebd425edb2f63
Author: dahn <[email protected]>
AuthorDate: Wed Apr 15 20:16:15 2026 +0200
upgrade guard explanation (#609)
* guard explanation
* Add example of trouble shooting
* Apply suggestions from code review
Co-authored-by: Abhisar Sinha <[email protected]>
---------
Co-authored-by: Daan Hoogland <[email protected]>
Co-authored-by: Abhisar Sinha <[email protected]>
---
source/upgrading/index.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/source/upgrading/index.rst b/source/upgrading/index.rst
index 11631b56..29b1812e 100644
--- a/source/upgrading/index.rst
+++ b/source/upgrading/index.rst
@@ -34,6 +34,17 @@ The `cloudstack-management` package will now include the
systemVM Templates for
either prior upgrade or during fresh installation, ACS will handle the
Template registration automatically, by mounting the secondary store onto the
management server, copying the respective Templates to the store and then
creating the `template.properties` file.
+From ACS 4.20.3 and 4.22.1 onwards, a starting Management Server that detects
an
+upgrade is needed will abort if it also finds mshost entries for other
Management Servers that are up.
+If as an operator starting a Management Server you get the error
+`Database upgrade is required but the management server is running in
+a clustered environment.` during upgrade, check if you have stopped
+all other Management Servers in your environment and retry. If it still fails,
it might be
+that a Management Server has stopped un-gracefully and you need to fix the
DB-entry
+for it. For example, make sure all Management Servers are stopped by checking
the
+hosts in the output of `select name from mshost where state <> ‘Down’`
+and then, when all is safe, run `update mshost set state = ‘Down'`
+
.. note::
For information on the API changes and issues fixed in this release, please
see the Release Notes section of the documentation
