cloudstack - simulator Stopped working

[Antonio Perpinan]

Hi I am teach cloudstack and the easiest way is using cloudstack/simulator

But recently it has completely stopped working.. any help, with this issue
which is a DB error during the setup or finding a similar software would be
highly appreciated.

--
Antonio Perpinan
Fundación
Código Libre Dominicano

Re: cloudstack - simulator Stopped working

[Nux]

Hello,

Can you please send some more information and logs?

---
Nux
www.nux.ro

On 2022-06-22 01:33, Antonio Perpinan wrote:
Hi I am teach cloudstack and the easiest way is using 
cloudstack/simulator


But recently it has completely stopped working.. any help, with this 
issue
which is a DB error during the setup or finding a similar software 
would be

highly appreciated.

--
Antonio Perpinan
Fundación
Código Libre Dominicano

[GitHub] [cloudstack-kubernetes-provider] tenvecera commented on issue #40: Affinity group for nodes

[GitBox]

tenvecera commented on issue #40:
URL: 
https://github.com/apache/cloudstack-kubernetes-provider/issues/40#issuecomment-1163096587

   Seems this repository isn't right place to raise this question.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-kubernetes-provider] tenvecera closed issue #40: Affinity group for nodes

[GitBox]

tenvecera closed issue #40: Affinity group for nodes
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/40


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: ACS Upgrade Failed :: Xenserver

[Gabriel Bräscher]

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 held broken
> > packages.root@cloudstack1:~#*
> > 
> >
> >
> > On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher 
> > 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  >
> >> wrote:
> >>
> >> > Hello,
> >> >
> >> > Thanks for getting back to me. Nothing specific in logs, getting
> >> following
> >> > error while we are trying to reinstall the services.
> >> >
> >> > =
> >> > root@cloudstack1:~# sudo apt-get --reinstall install cloudstack-usage
> >> > Reading package lists... Done
> >> > Building dependency tree
> >> > Reading state information... Done
> >> > Some packages could not be installed. This may mean that you have
> >> > requested an impossible situation or if you are using the unstable
> >> > distribution that some required packages have not yet been created
> >> > or been moved out of Incoming.
> >> > The following information may help to resolve the situation:
> >> >
> >> > The following packages have unmet dependencies:
> >> >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
> >> > 4.17.0.0~bionic is to be installed
> >> > E: Unable to correct problems, you have held broken packages.
> >> > =
> >> >
> >> > Thank you,
> >> > Ranjit
> >> >
> >> > On Mon, 20 Jun 2022 at 08:17, Harikrishna Patnala <
> >> > harikrishna.patn...@shapeblue.com> wrote:
> >> >
> >> > > Hi Ranjit,
> >> > >
> >> > > CloudStack manage

Re: ACS Upgrade Failed :: Xenserver

[Ranjit Jadhav]

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 held broken
> > > packages.root@cloudstack1:~#*
> > > 
> > >
> > >
> > > On Mon, 20 Jun 2022 at 18:51, Gabriel Bräscher 
> > > 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