Skip to content

upgrade guard explanation #609

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DaanHoogland wants to merge 2 commits into
base: 4.20
Choose a base branch
from
+11 −0
Open

upgrade guard explanation #609

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4cebc10
guard explanation
Dec 12, 2025
9fa54fa
Add example of trouble shooting
DaanHoogland Dec 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions source/upgrading/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 MS that detects an
Copy link
Copy Markdown
Collaborator

@abh1sar abh1sar Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
From ACS 4.20.3 and 4.22.1 onwards A starting MS that detects an
From ACS 4.20.3 and 4.22.1 onwards, a starting MS that detects that an

upgrade is needed but also sees mshost entries for MSses that are up,
will abort. If as an operator starting an MS 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 MSses in your environment and retry. If is still fails it might be
that an MS has stopped un-gracefully and you need to fix the DB-entry
Copy link
Copy Markdown
Member

@weizhouapache weizhouapache Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add an example how to fix in db ?

Copy link
Copy Markdown
Contributor Author

@DaanHoogland DaanHoogland Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added an example, can you see if such is what you mean, @weizhouapache ?

for it. For example, make sure all MSses 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

Expand Down