Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1684
@jburwell when a fresh mgmt server is deployed for upgrading an existing
CloudStack environment, several files from `/etc/cloudstack/management` are
copied to the new server, especially the `db.properties` file. The
`commands.properties` is no different, in the past all such deployment (where
in-place upgrades were avoided) copied all these config files in
/etc/cloudstack/management from old server to new server.
Official docs only talk about in-place upgrades, our packaging system
(post-install/upgrade scripts) assume in-place upgrade as well; if someone's
doing fresh mgmt server for upgrade, they know what they are doing and its
out-of-scope of what the project can support. At the same time, we may add
documentation for such kind of upgrades as well. The solution for this problem
is documentation and release/upgrade notes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
