Venmo

2022-06-24 Thread Katie F.



Sent from my iPhoneSE.Kathleen Foos


Re: ACS Upgrade Failed :: Xenserver

2022-06-24 Thread Gabriel Bräscher
Hi Ranjit,

Great to hear that all is good!

Best regards,
Gabriel.

On Fri, Jun 24, 2022 at 8:16 AM Ranjit Jadhav 
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 
> 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
> > " 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 
> > 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  >
> >> 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  >
> >> > 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 

Build fails in macOS

2022-06-24 Thread Pritam Neog
Hi all

I was trying to build cloudstack from source but it fails to build the Apache 
CloudStack marvin 4.17.0.0 pom.

This is the error produced:

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(package) on project cloud-marvin: Command execution failed.: Cannot run 
program "python" (in directory "/Users/neog/acs/cloudstack/tools/marvin"): 
error=2, No such file or directory

But the directory exists and I’ve edited my sudoers file to grant cloudstack 
root access.

Previously, the build was failing at apidoc pom where ‘python’ was not 
recognised by maven even after setting alias for python=python3 and it works 
flawlessly elsewhere. I fixed it by editing out all python occurrences to 
python3 in tools/apidoc/build-apidoc.sh 

Environment:
OS name: "mac os x”
version: “12.4"
arch: “aarch64"
family: "mac"

Re: ACS Upgrade Failed :: Xenserver

2022-06-24 Thread Ranjit Jadhav
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 
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
> " 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 
> 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 
>> 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 
>> > 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