Hi, It is a good approach and should work. You do not need to make any database changes manually. During CloudStack start, it will detect the cloudstack version in the database and cloudstack version on the management server , and perform database upgrades if the versions are not the same.
It looks like something is wrong during cloudstack start, please check the logs. -Wei On Tue, 12 Sept 2023 at 13:11, Francisco Arencibia Quesada < [email protected]> wrote: > Good morning guys, > > We have installed a new machine with 4.17 and we are pointing to the > database of the old machine and it is not working, we receive the following > error message: > HTTP ERROR 503 Service Unavailable > URI: /client/ > STATUS: 503 > MESSAGE: Service Unavailable > SERVLET: - > > > Summarizing: > The old machine with cloudstack 4.11.2 is stopped > new machine with 4.17 is up and pointing out to the database from the old > machine with 4.11.2. > > Is this a good approach? Can we make it work,? or we need to make some > changes in the database to support 4.17. > > Kind regards > > > > -- > *Francisco Arencibia Quesada.* > *DevOps Engineer* >
