You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "DaanHoogland (via GitHub)" <gi...@apache.org> on 2025/12/12 14:41:49 UTC
[PR] upgrade guard explanation [cloudstack-documentation]
DaanHoogland opened a new pull request, #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r2626995760
##########
source/upgrading/index.rst:
##########
@@ -34,6 +34,15 @@ 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
+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
Review Comment:
I added an example, can you see if such is what you mean, @weizhouapache ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r3085889982
##########
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 MS that detects 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
Review Comment:
```suggestion
that a Management Server has stopped un-gracefully and you need to fix the DB-entry
```
##########
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 MS that detects 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
+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'`
Review Comment:
```suggestion
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'`
```
##########
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 MS that detects 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
Review Comment:
```suggestion
all other Management Servers in your environment and retry. If it still fails, it might be
```
##########
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 MS that detects 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
Review Comment:
```suggestion
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
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r2614656718
##########
source/upgrading/index.rst:
##########
@@ -34,6 +34,15 @@ 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
+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
Review Comment:
add an example how to fix in db ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r3063014494
##########
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 MS that detects an
Review Comment:
```suggestion
From ACS 4.20.3 and 4.22.1 onwards, a starting MS that detects that an
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar merged PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r2626990894
##########
source/upgrading/index.rst:
##########
@@ -34,6 +34,15 @@ 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
+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
+for it.
Review Comment:
```suggestion
From ACS 4.20.3 and 4.22.1 onwards A starting MS that detects 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
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'`
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] upgrade guard explanation [cloudstack-documentation]
Posted by "abh1sar (via GitHub)" <gi...@apache.org>.
abh1sar commented on code in PR #609:
URL: https://github.com/apache/cloudstack-documentation/pull/609#discussion_r3063014494
##########
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 MS that detects an
Review Comment:
```suggestion
From ACS 4.20.3 and 4.22.1 onwards, a starting MS that detects that an
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org