Sanjay, You should upgrade all your management servers and KVM agents to the same version. Did you or your team try to downgraded some package after an upgrade?
Generally speaking, you can consider the latest ACS release. You may review and upgrade to 4.18.2.1 or 4.18.2.2 which is currently the most recent LTS/4.18 release https://cloudstack.apache.org/blog/security-release-advisory-cve-2024-41107 Regards. ________________________________ From: Sanjay Kumar <sslinuxp...@gmail.com> Sent: Monday, July 29, 2024 10:29 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 help! I have one more question, can go with 4.18.1.1 or upgrade to 4.18.2.2? I read some blogs by Rohit Yadav and found some security-related information on 4.18.1.1 https://cloudstack.apache.org/blog/security-release-advisory-4.19.0.1-4.18.1.1/ Please suggest. Thank you S Kumar Sanjay Kumar KV IT-Solutions Pvt. Ltd. m: 9891015813 a: 26th ,Badarpur Delhi s: sslinuxpath.blogspot.in e: sslinuxp...@gmail.com <https://www.facebook.com/kumarsanjay07> <https://in.linkedin.com/in/sslinuxpath> On Mon, Jul 29, 2024 at 10:24 AM Jithin Raju <jithin.r...@shapeblue.com> wrote: > 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 > > > > > > > > > > > >
