Hi Sanjay, For RPM based distros here is the method:
https://serverdiary.com/linux/how-to-yum-update-to-specific-version/ -Jithin From: Sanjay Kumar <sslinuxp...@gmail.com> Date: Monday, 29 July 2024 at 10:19 AM To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: After restart the service of acs it's showing [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = 4.18.1.1 Code Version = 4.18.1.0 Hi Jithin, Thanks for the quick response! Both management and KVM were on the same version of 4.18.1.0 but recently we restarted the management server first and second after that first management server showed on 4.18.1.1 and the second showed 4.18.1.0. When we try to upgrade the second management server it goes to 4.18.2.2, not on 4.18.1.1. How cloud be upgraded to the same version as 4.18.1.1? Thank you S Kumar On Mon, Jul 29, 2024 at 10:12 AM Jithin Raju <jithin.r...@shapeblue.com> wrote: > Hi Sanjay, > > Both management servers and if any KVM agents should be on the same > version, you should be upgrading the second management server to 4.18.1.1. > > -Jithin > > From: Sanjay Kumar <sslinuxp...@gmail.com> > Date: Monday, 29 July 2024 at 10:07 AM > To: us...@cloudstack.apache.org <us...@cloudstack.apache.org> > Cc: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: After restart the service of acs it's showing > [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = 4.18.1.1 > Code Version = 4.18.1.0 > Hello! > > It's a strange issue found recently, we restarted acs service and got the > error [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = > 4.18.1.1 Code Version = 4.18.1.0. Is there any issue of the impact of > infra? the acs first is showing on 4.18.1.1 and acs second is showing on > 4.18.1.0 and earlier it was running on 4.18.1.0. > > ACS01: 4.18.1.0 > ACS02: 4.18.1.0 > > Any help would be really appreciated. Thank you! > > Regards, > S Kumar > > > >
