You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Ranjit Jadhav <ra...@gmail.com> on 2022/06/18 12:23:14 UTC
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
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
Hi Ranjit,
Great to hear that all is good!
Best regards,
Gabriel.
On Fri, Jun 24, 2022 at 8:16 AM Ranjit Jadhav <ra...@gmail.com>
wrote:
> Hello Gabriel ..... Harikrishna ,
>
> Everything looks good now, the upgrade process was completed.
>
> Thank you very much for your assistance.
>
>
>
> On Thu, 23 Jun 2022 at 02:18, Ranjit Jadhav <ra...@gmail.com>
> wrote:
>
> > Thanks for getting back to me, here are the required details from our
> > setup. Upgrade went well without any errors, but SystemVM are not
> upgraded
> > yet.
> > Check for the screenshot attached. I can see "label.guest.vlan
> > <http://103.13.114.141:8080/client/#/guestvlans>" section added under
> > Network though.
> >
> >
> > root@cloudstack1:~# apt list --installed -a cloudstack-management
> > Listing... Done
> > cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
> > cloudstack-management/bionic 4.16.1.0~bionic all
> > cloudstack-management/bionic 4.16.0.0~bionic all
> >
> >
> ==========================================================================
> >
> > root@cloudstack1:~# apt list --installed -a cloudstack-usage
> > Listing... Done
> > cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
> > cloudstack-usage/bionic 4.16.1.0~bionic all
> > cloudstack-usage/bionic 4.16.0.0~bionic all
> >
> >
> ==========================================================================
> >
> > root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
> > #deb http://download.cloudstack.org/ubuntu bionic 4.15
> > deb http://download.cloudstack.org/ubuntu bionic 4.16
> > deb http://download.cloudstack.org/ubuntu bionic 4.17
> >
> > Thank you,
> > Ranjit
> >
> > On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com>
> > wrote:
> >
> >> Ranji, sorry by the delay.
> >>
> >> Can you please share what is the configuration set in
> >> /etc/apt/sources.list.d/cloudstack.list?
> >> should be something such as "deb http://download.cloudstack.org/ubuntu
> >> bionic 4.17".
> >>
> >> I've just managed to install it but noticed that the mirror needed to
> >> resync (some cache or something was not right).
> >>
> >> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
> >> Setting up cloudstack-usage (4.17.0.0~bionic) ...
> >> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic
> !
> >>
> >> * Project website: https://cloudstack.apache.org/
> >> * Documentation:
> >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
> >> * Release notes:
> >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
> >> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
> >> * Take the survey: https://cloudstack.apache.org/survey.html
> >> * Report issues: https://github.com/apache/cloudstack/issues/new
> >>
> >> Created symlink
> >> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
> >> /lib/systemd/system/cloudstack-usage.service.
> >>
> >> Can you please re-try?
> >> Might require updating the apt sources list and running "apt-get update"
> >> again?
> >>
> >> Best regards,
> >> Gabriel.
> >>
> >>
> >>
> >> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ranjeet.jadhav@gmail.com
> >
> >> wrote:
> >>
> >> > 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.jadhav@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 <
> gabrascher@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> >> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
> >> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
> >> dev
> >> > <
> >> > >> > > dev@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
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
Hi Ranjit,
Great to hear that all is good!
Best regards,
Gabriel.
On Fri, Jun 24, 2022 at 8:16 AM Ranjit Jadhav <ra...@gmail.com>
wrote:
> Hello Gabriel ..... Harikrishna ,
>
> Everything looks good now, the upgrade process was completed.
>
> Thank you very much for your assistance.
>
>
>
> On Thu, 23 Jun 2022 at 02:18, Ranjit Jadhav <ra...@gmail.com>
> wrote:
>
> > Thanks for getting back to me, here are the required details from our
> > setup. Upgrade went well without any errors, but SystemVM are not
> upgraded
> > yet.
> > Check for the screenshot attached. I can see "label.guest.vlan
> > <http://103.13.114.141:8080/client/#/guestvlans>" section added under
> > Network though.
> >
> >
> > root@cloudstack1:~# apt list --installed -a cloudstack-management
> > Listing... Done
> > cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
> > cloudstack-management/bionic 4.16.1.0~bionic all
> > cloudstack-management/bionic 4.16.0.0~bionic all
> >
> >
> ==========================================================================
> >
> > root@cloudstack1:~# apt list --installed -a cloudstack-usage
> > Listing... Done
> > cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
> > cloudstack-usage/bionic 4.16.1.0~bionic all
> > cloudstack-usage/bionic 4.16.0.0~bionic all
> >
> >
> ==========================================================================
> >
> > root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
> > #deb http://download.cloudstack.org/ubuntu bionic 4.15
> > deb http://download.cloudstack.org/ubuntu bionic 4.16
> > deb http://download.cloudstack.org/ubuntu bionic 4.17
> >
> > Thank you,
> > Ranjit
> >
> > On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com>
> > wrote:
> >
> >> Ranji, sorry by the delay.
> >>
> >> Can you please share what is the configuration set in
> >> /etc/apt/sources.list.d/cloudstack.list?
> >> should be something such as "deb http://download.cloudstack.org/ubuntu
> >> bionic 4.17".
> >>
> >> I've just managed to install it but noticed that the mirror needed to
> >> resync (some cache or something was not right).
> >>
> >> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
> >> Setting up cloudstack-usage (4.17.0.0~bionic) ...
> >> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic
> !
> >>
> >> * Project website: https://cloudstack.apache.org/
> >> * Documentation:
> >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
> >> * Release notes:
> >> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
> >> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
> >> * Take the survey: https://cloudstack.apache.org/survey.html
> >> * Report issues: https://github.com/apache/cloudstack/issues/new
> >>
> >> Created symlink
> >> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
> >> /lib/systemd/system/cloudstack-usage.service.
> >>
> >> Can you please re-try?
> >> Might require updating the apt sources list and running "apt-get update"
> >> again?
> >>
> >> Best regards,
> >> Gabriel.
> >>
> >>
> >>
> >> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ranjeet.jadhav@gmail.com
> >
> >> wrote:
> >>
> >> > 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.jadhav@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 <
> gabrascher@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> >> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
> >> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
> >> dev
> >> > <
> >> > >> > > dev@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
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
Hello Gabriel ..... Harikrishna ,
Everything looks good now, the upgrade process was completed.
Thank you very much for your assistance.
On Thu, 23 Jun 2022 at 02:18, Ranjit Jadhav <ra...@gmail.com>
wrote:
> Thanks for getting back to me, here are the required details from our
> setup. Upgrade went well without any errors, but SystemVM are not upgraded
> yet.
> Check for the screenshot attached. I can see "label.guest.vlan
> <http://103.13.114.141:8080/client/#/guestvlans>" section added under
> Network though.
>
>
> root@cloudstack1:~# apt list --installed -a cloudstack-management
> Listing... Done
> cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
> cloudstack-management/bionic 4.16.1.0~bionic all
> cloudstack-management/bionic 4.16.0.0~bionic all
>
> ==========================================================================
>
> root@cloudstack1:~# apt list --installed -a cloudstack-usage
> Listing... Done
> cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
> cloudstack-usage/bionic 4.16.1.0~bionic all
> cloudstack-usage/bionic 4.16.0.0~bionic all
>
> ==========================================================================
>
> root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
> #deb http://download.cloudstack.org/ubuntu bionic 4.15
> deb http://download.cloudstack.org/ubuntu bionic 4.16
> deb http://download.cloudstack.org/ubuntu bionic 4.17
>
> Thank you,
> Ranjit
>
> On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com>
> wrote:
>
>> Ranji, sorry by the delay.
>>
>> Can you please share what is the configuration set in
>> /etc/apt/sources.list.d/cloudstack.list?
>> should be something such as "deb http://download.cloudstack.org/ubuntu
>> bionic 4.17".
>>
>> I've just managed to install it but noticed that the mirror needed to
>> resync (some cache or something was not right).
>>
>> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
>> Setting up cloudstack-usage (4.17.0.0~bionic) ...
>> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
>>
>> * Project website: https://cloudstack.apache.org/
>> * Documentation:
>> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
>> * Release notes:
>> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
>> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
>> * Take the survey: https://cloudstack.apache.org/survey.html
>> * Report issues: https://github.com/apache/cloudstack/issues/new
>>
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
>> /lib/systemd/system/cloudstack-usage.service.
>>
>> Can you please re-try?
>> Might require updating the apt sources list and running "apt-get update"
>> again?
>>
>> Best regards,
>> Gabriel.
>>
>>
>>
>> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
>> wrote:
>>
>> > 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
>> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
>> dev
>> > <
>> > >> > > dev@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
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> >
>>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
Hello Gabriel ..... Harikrishna ,
Everything looks good now, the upgrade process was completed.
Thank you very much for your assistance.
On Thu, 23 Jun 2022 at 02:18, Ranjit Jadhav <ra...@gmail.com>
wrote:
> Thanks for getting back to me, here are the required details from our
> setup. Upgrade went well without any errors, but SystemVM are not upgraded
> yet.
> Check for the screenshot attached. I can see "label.guest.vlan
> <http://103.13.114.141:8080/client/#/guestvlans>" section added under
> Network though.
>
>
> root@cloudstack1:~# apt list --installed -a cloudstack-management
> Listing... Done
> cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
> cloudstack-management/bionic 4.16.1.0~bionic all
> cloudstack-management/bionic 4.16.0.0~bionic all
>
> ==========================================================================
>
> root@cloudstack1:~# apt list --installed -a cloudstack-usage
> Listing... Done
> cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
> cloudstack-usage/bionic 4.16.1.0~bionic all
> cloudstack-usage/bionic 4.16.0.0~bionic all
>
> ==========================================================================
>
> root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
> #deb http://download.cloudstack.org/ubuntu bionic 4.15
> deb http://download.cloudstack.org/ubuntu bionic 4.16
> deb http://download.cloudstack.org/ubuntu bionic 4.17
>
> Thank you,
> Ranjit
>
> On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com>
> wrote:
>
>> Ranji, sorry by the delay.
>>
>> Can you please share what is the configuration set in
>> /etc/apt/sources.list.d/cloudstack.list?
>> should be something such as "deb http://download.cloudstack.org/ubuntu
>> bionic 4.17".
>>
>> I've just managed to install it but noticed that the mirror needed to
>> resync (some cache or something was not right).
>>
>> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
>> Setting up cloudstack-usage (4.17.0.0~bionic) ...
>> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
>>
>> * Project website: https://cloudstack.apache.org/
>> * Documentation:
>> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
>> * Release notes:
>> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
>> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
>> * Take the survey: https://cloudstack.apache.org/survey.html
>> * Report issues: https://github.com/apache/cloudstack/issues/new
>>
>> Created symlink
>> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
>> /lib/systemd/system/cloudstack-usage.service.
>>
>> Can you please re-try?
>> Might require updating the apt sources list and running "apt-get update"
>> again?
>>
>> Best regards,
>> Gabriel.
>>
>>
>>
>> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
>> wrote:
>>
>> > 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
>> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
>> dev
>> > <
>> > >> > > dev@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
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> >
>>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
Thanks for getting back to me, here are the required details from our
setup. Upgrade went well without any errors, but SystemVM are not upgraded
yet.
Check for the screenshot attached. I can see "label.guest.vlan
<http://103.13.114.141:8080/client/#/guestvlans>" section added under
Network though.
root@cloudstack1:~# apt list --installed -a cloudstack-management
Listing... Done
cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
cloudstack-management/bionic 4.16.1.0~bionic all
cloudstack-management/bionic 4.16.0.0~bionic all
==========================================================================
root@cloudstack1:~# apt list --installed -a cloudstack-usage
Listing... Done
cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
cloudstack-usage/bionic 4.16.1.0~bionic all
cloudstack-usage/bionic 4.16.0.0~bionic all
==========================================================================
root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
#deb http://download.cloudstack.org/ubuntu bionic 4.15
deb http://download.cloudstack.org/ubuntu bionic 4.16
deb http://download.cloudstack.org/ubuntu bionic 4.17
Thank you,
Ranjit
On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com> wrote:
> Ranji, sorry by the delay.
>
> Can you please share what is the configuration set in
> /etc/apt/sources.list.d/cloudstack.list?
> should be something such as "deb http://download.cloudstack.org/ubuntu
> bionic 4.17".
>
> I've just managed to install it but noticed that the mirror needed to
> resync (some cache or something was not right).
>
> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
> Setting up cloudstack-usage (4.17.0.0~bionic) ...
> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
>
> * Project website: https://cloudstack.apache.org/
> * Documentation:
> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
> * Release notes:
> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
> * Take the survey: https://cloudstack.apache.org/survey.html
> * Report issues: https://github.com/apache/cloudstack/issues/new
>
> Created symlink
> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
> /lib/systemd/system/cloudstack-usage.service.
>
> Can you please re-try?
> Might require updating the apt sources list and running "apt-get update"
> again?
>
> Best regards,
> Gabriel.
>
>
>
> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
> wrote:
>
> > 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
> dev
> > <
> > >> > > dev@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
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
Thanks for getting back to me, here are the required details from our
setup. Upgrade went well without any errors, but SystemVM are not upgraded
yet.
Check for the screenshot attached. I can see "label.guest.vlan
<http://103.13.114.141:8080/client/#/guestvlans>" section added under
Network though.
root@cloudstack1:~# apt list --installed -a cloudstack-management
Listing... Done
cloudstack-management/bionic,now 4.17.0.0~bionic all [installed]
cloudstack-management/bionic 4.16.1.0~bionic all
cloudstack-management/bionic 4.16.0.0~bionic all
==========================================================================
root@cloudstack1:~# apt list --installed -a cloudstack-usage
Listing... Done
cloudstack-usage/bionic,now 4.17.0.0~bionic all [installed]
cloudstack-usage/bionic 4.16.1.0~bionic all
cloudstack-usage/bionic 4.16.0.0~bionic all
==========================================================================
root@cloudstack1:~# cat /etc/apt/sources.list.d/cloudstack.list
#deb http://download.cloudstack.org/ubuntu bionic 4.15
deb http://download.cloudstack.org/ubuntu bionic 4.16
deb http://download.cloudstack.org/ubuntu bionic 4.17
Thank you,
Ranjit
On Wed, 22 Jun 2022 at 21:43, Gabriel Bräscher <ga...@gmail.com> wrote:
> Ranji, sorry by the delay.
>
> Can you please share what is the configuration set in
> /etc/apt/sources.list.d/cloudstack.list?
> should be something such as "deb http://download.cloudstack.org/ubuntu
> bionic 4.17".
>
> I've just managed to install it but noticed that the mirror needed to
> resync (some cache or something was not right).
>
> Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
> Setting up cloudstack-usage (4.17.0.0~bionic) ...
> Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
>
> * Project website: https://cloudstack.apache.org/
> * Documentation:
> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
> * Release notes:
> https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
> * Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
> * Take the survey: https://cloudstack.apache.org/survey.html
> * Report issues: https://github.com/apache/cloudstack/issues/new
>
> Created symlink
> /etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
> /lib/systemd/system/cloudstack-usage.service.
>
> Can you please re-try?
> Might require updating the apt sources list and running "apt-get update"
> again?
>
> Best regards,
> Gabriel.
>
>
>
> On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
> wrote:
>
> > 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> > >> > > Sent: Saturday, June 18, 2022 5:53 PM
> > >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>;
> dev
> > <
> > >> > > dev@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
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
Ranji, sorry by the delay.
Can you please share what is the configuration set in
/etc/apt/sources.list.d/cloudstack.list?
should be something such as "deb http://download.cloudstack.org/ubuntu
bionic 4.17".
I've just managed to install it but noticed that the mirror needed to
resync (some cache or something was not right).
Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
Setting up cloudstack-usage (4.17.0.0~bionic) ...
Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
* Project website: https://cloudstack.apache.org/
* Documentation:
https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
* Release notes:
https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
* Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
* Take the survey: https://cloudstack.apache.org/survey.html
* Report issues: https://github.com/apache/cloudstack/issues/new
Created symlink
/etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
/lib/systemd/system/cloudstack-usage.service.
Can you please re-try?
Might require updating the apt sources list and running "apt-get update"
again?
Best regards,
Gabriel.
On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
wrote:
> 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> >> > > Sent: Saturday, June 18, 2022 5:53 PM
> >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev
> <
> >> > > dev@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
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
Ranji, sorry by the delay.
Can you please share what is the configuration set in
/etc/apt/sources.list.d/cloudstack.list?
should be something such as "deb http://download.cloudstack.org/ubuntu
bionic 4.17".
I've just managed to install it but noticed that the mirror needed to
resync (some cache or something was not right).
Compiling '/usr/lib/python3/dist-packages/cloudutils/utilities.py'...
Setting up cloudstack-usage (4.17.0.0~bionic) ...
Thank you for installing Apache CloudStack Usage Server 4.17.0.0~bionic !
* Project website: https://cloudstack.apache.org/
* Documentation:
https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/
* Release notes:
https://docs.cloudstack.apache.org/en/4.17.0.0~bionic/releasenotes/
* Join mailing lists: https://cloudstack.apache.org/mailing-lists.html
* Take the survey: https://cloudstack.apache.org/survey.html
* Report issues: https://github.com/apache/cloudstack/issues/new
Created symlink
/etc/systemd/system/multi-user.target.wants/cloudstack-usage.service →
/lib/systemd/system/cloudstack-usage.service.
Can you please re-try?
Might require updating the apt sources list and running "apt-get update"
again?
Best regards,
Gabriel.
On Tue, Jun 21, 2022 at 8:22 PM Ranjit Jadhav <ra...@gmail.com>
wrote:
> 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 <ra...@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 <ga...@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.jadhav@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.Patnala@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 <ra...@gmail.com>
> >> > > Sent: Saturday, June 18, 2022 5:53 PM
> >> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev
> <
> >> > > dev@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
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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 <ra...@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 <ga...@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 <ra...@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.Patnala@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 <ra...@gmail.com>
>> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
>> > > dev@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
>> > >
>> > >
>> > >
>> > >
>> >
>>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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 <ra...@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 <ga...@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 <ra...@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.Patnala@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 <ra...@gmail.com>
>> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
>> > > dev@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
>> > >
>> > >
>> > >
>> > >
>> >
>>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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 <ga...@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 <ra...@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.Patnala@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 <ra...@gmail.com>
> > > Sent: Saturday, June 18, 2022 5:53 PM
> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> > > dev@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
> > >
> > >
> > >
> > >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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 <ga...@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 <ra...@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.Patnala@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 <ra...@gmail.com>
> > > Sent: Saturday, June 18, 2022 5:53 PM
> > > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> > > dev@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
> > >
> > >
> > >
> > >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
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 <ra...@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.Patnala@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 <ra...@gmail.com>
> > Sent: Saturday, June 18, 2022 5:53 PM
> > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> > dev@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
> >
> >
> >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Gabriel Bräscher <ga...@gmail.com>.
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 <ra...@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.Patnala@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 <ra...@gmail.com>
> > Sent: Saturday, June 18, 2022 5:53 PM
> > To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> > dev@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
> >
> >
> >
> >
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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.Patnala@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 <ra...@gmail.com>
> Sent: Saturday, June 18, 2022 5:53 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> dev@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
>
>
>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Ranjit Jadhav <ra...@gmail.com>.
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.Patnala@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 <ra...@gmail.com>
> Sent: Saturday, June 18, 2022 5:53 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <
> dev@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
>
>
>
>
Re: ACS Upgrade Failed :: Xenserver
Posted by Harikrishna Patnala <Ha...@shapeblue.com>.
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 <ra...@gmail.com>
Sent: Saturday, June 18, 2022 5:53 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <de...@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
Re: ACS Upgrade Failed :: Xenserver
Posted by Harikrishna Patnala <Ha...@shapeblue.com>.
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 <ra...@gmail.com>
Sent: Saturday, June 18, 2022 5:53 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; dev <de...@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