borisstoyanov opened a new issue, #11973: URL: https://github.com/apache/cloudstack/issues/11973
### problem A user might execute an incident upgrade when adding a new management server with later version(if let's say there's a new minor version meanwhile in the same upstream repo). To avoid this, I propose when we identify an upgrade path is due we: 1. Check DB if there's any other management server in Up state 2. If yes, we skip the DB upgrade and shut down the management server. ### versions any, detected with 4.20.1 env and recent 4.20.2 release ### The steps to reproduce the bug 1. Have an env running 4.20.1 2. Add new management server, with version 4.20.2 3. Start the management server ... ### What to do about it? _No response_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
