While trying to switch back to Bionic from Focal, please advice ==================================================== root@cloudstack1:~# sudo apt-get install cloudstack-management=4.17.0.0~bionic Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: cloudstack-management : Depends: cloudstack-common (= 4.17.0.0~bionic) but 4.17.0.0~focal is to be installed E: Unable to correct problems, you have held broken packages. root@cloudstack1:~# On Tue, 21 Jun 2022 at 18:32, Ranjit Jadhav <ranjeet.jad...@gmail.com> wrote: > Hello, > > Thanks for the update, I tried with bionic but got the error below. After > changing to focal it worked, both management and usage services are online. > But the SystemVM version is still 4.16.1. Shall we import the template > again? What should be the approach now. > > ============================================ > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > > or been moved out of Incoming. > The following information may help to resolve the situation: > > > > > *The following packages have unmet dependencies: cloudstack-usage : > Depends: cloudstack-common (= 4.17.0.0~focal) but 4.17.0.0~bionic is to be > installedE: Unable to correct problems, you have held broken > packages.root@cloudstack1:~#* > ============================================ > > > On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher <gabrasc...@gmail.com> > wrote: > >> Ranjit can you please try the upgrade again? >> >> There was an issue with the mirror for the usage package (4.17.0.0 bionic >> only). >> Should be good now (the mirror might still be syncing, but I bet it is >> already good to go). >> >> Regards, >> Gabriel. >> >> On Mon, Jun 20, 2022 at 6:15 AM Ranjit Jadhav <ranjeet.jad...@gmail.com> >> wrote: >> >> > Hello, >> > >> > Thanks for getting back to me. Nothing specific in logs, getting >> following >> > error while we are trying to reinstall the services. >> > >> > ============================= >> > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage >> > Reading package lists... Done >> > Building dependency tree >> > Reading state information... Done >> > Some packages could not be installed. This may mean that you have >> > requested an impossible situation or if you are using the unstable >> > distribution that some required packages have not yet been created >> > or been moved out of Incoming. >> > The following information may help to resolve the situation: >> > >> > The following packages have unmet dependencies: >> > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but >> > 4.17.0.0~bionic is to be installed >> > E: Unable to correct problems, you have held broken packages. >> > ============================= >> > >> > Thank you, >> > Ranjit >> > >> > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala < >> > harikrishna.patn...@shapeblue.com> wrote: >> > >> > > Hi Ranjit, >> > > >> > > CloudStack management and usage have to be on the same version, can >> you >> > > please check the version of CloudStack usage server and verify if the >> > > upgrade to 4.17 happened properly. If not on 4.17, can you please try >> to >> > > upgrade the usage server? >> > > >> > > Please paste the exact error from the management server or usage >> server >> > > logs that you are seeing. >> > > >> > > Thanks, >> > > Harikrishna >> > > >> > > ________________________________ >> > > From: Ranjit Jadhav <ranjeet.jad...@gmail.com> >> > > Sent: Saturday, June 18, 2022 5:53 PM >> > > To: users@cloudstack.apache.org <users@cloudstack.apache.org>; dev < >> > > d...@cloudstack.apache.org> >> > > Subject: ACS Upgrade Failed :: Xenserver >> > > >> > > Hello, >> > > >> > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we >> > faced >> > > the following issue. It appears that "cloudstack-management" and >> > > "cloudstack-usage" requires different versions of cloudstack-common. >> > > >> > > With cloudstack-common=4.17 Management, services are working but Usage >> > > services are asking for 4.16.1.0~bionic >> > > >> > > ================================== >> > > The following packages have unmet dependencies: >> > > cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but >> > > 4.17.0.0~bionic is to be installed >> > > E: Unable to correct problems, you have held broken packages. >> > > ================================== >> > > >> > > We followed the steps below to upgrade ACS >> > > >> > > >> > > >> > >> https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers >> > > >> > > The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng) >> > > >> > > Any guidance would be appreciated. >> > > >> > > Thank you >> > > >> > > >> > > >> > > >> > >> >
