Re: ACS Upgrade Failed :: Xenserver

2022-06-21 Thread Ranjit Jadhav 
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 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 
>> > > Sent: Saturday, June 18, 2022 5:53 PM
>> > > To: users@cloudstack.apache.org ; dev <
>> > > d...@cloudstack.apache.org>
>> > > Subject: ACS Upgrade Failed :: Xenserver
>> > >
>> > > Hello,
>> > >
>> > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we
>> > faced
>> > > the following issue. It appears that "cloudstack-management" and
>> > > "cloudstack-usage" requires different versions of cloudstack-common.
>> > >
>> > > With cloudstack-common=4.17 Management, services are working but Usage
>> > > services are asking for 4.16.1.0~bionic
>> > >
>> > > ==
>> > > The following packages have unmet dependencies:
>> > >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
>> > > 4.17.0.0~bionic is to be installed
>> > > E: Unable to correct problems, you have held broken packages.
>> > > ==
>> > >
>> > > We followed the steps below to upgrade ACS
>> > >
>> > >
>>

Re: ACS Upgrade Failed :: Xenserver

2022-06-21 Thread Ranjit Jadhav 
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 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 
> > > Sent: Saturday, June 18, 2022 5:53 PM
> > > To: users@cloudstack.apache.org ; dev <
> > > d...@cloudstack.apache.org>
> > > Subject: ACS Upgrade Failed :: Xenserver
> > >
> > > Hello,
> > >
> > > While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we
> > faced
> > > the following issue. It appears that "cloudstack-management" and
> > > "cloudstack-usage" requires different versions of cloudstack-common.
> > >
> > > With cloudstack-common=4.17 Management, services are working but Usage
> > > services are asking for 4.16.1.0~bionic
> > >
> > > ==
> > > The following packages have unmet dependencies:
> > >  cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
> > > 4.17.0.0~bionic is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > > ==
> > >
> > > We followed the steps below to upgrade ACS
> > >
> > >
> > >
> >
> https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers
> > >
> > > The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng)
> > >
> > > Any guidance would be appreciated.
> > >
> > > Thank you
> > >
> > >
> > >
> > >
> >
>

Re: Certificate Expired

2022-06-21 Thread Nux 


Have you tried reconfiguring the cert on that host?

There's a UI button for it in the host page as well as an API call:

---
Nux
www.nux.ro [1]

On 2022-06-20 17:12, Bs Serge wrote:


Hypervisor: KVM
Management  OS: Centos 8
Host OS: Centos 8
CloudStack 4.15.0.0

Hi all,

Cloudstack was working well for a long time until a server restart 
occurred

and now Libvirt says the server certificate is expired.

Libvirt Logs :

Jun 20 05:36:30 srvr2 systemd[1]: Starting Virtualization daemon...
Jun 20 05:36:30 srvr2 journal[4092]: libvirt version: 6.0.0, package:
28.1.module_el8.3.0+755+88436ea4 (CentOS Buildsys ,
2021-04-07-02:51:43, )
Jun 20 05:36:30 srvr2 journal[4092]: hostname: srvr2.cloud.priv
Jun 20 05:36:30 srvr2 journal[4092]: The server certificate
/etc/pki/libvirt/servercert.pem has expired
Jun 20 05:36:30 srvr2 systemd[1]: libvirtd.service: Main process 
exited,

code=exited, status=6/NOTCONFIGURED
Jun 20 05:36:30 srvr2 systemd[1]: libvirtd.service: Failed with result
'exit-code'.
Jun 20 05:36:30 srvr2 systemd[1]: Failed to start Virtualization 
daemon.


This guide seems to not be helping:
https://blog.diaboliko.net/linux/rhel7-deal-kvm-certificate-expiration/

Any thoughts or comments would be appreciated!

Best regards,



Links:
--
[1] http://www.nux.ro

CFP - CloudStack Collaboration Conference

2022-06-21 Thread Jamie Pell 
Hi all,

Just a reminder that the CFP is open for CloudStack Collaboration Conference 
2022.

I would encourage anyone interested in submitting a talk to do so sooner than 
later, to help maximise the chance of being accepted 
-https://docs.google.com/forms/d/e/1FAIpQLSeE2o9IZTVHaPvsBJXQW2gZjZqxjZ7CynUJb9MZ22s7uyzyDA/viewform

If you have any questions, feel free to ask.

Kind regards,

No input filed for IP address in UI when adding new Zone

2022-06-21 Thread cristian.c 
Hello,

 

   Did anyone added a new zone via UI in cloudstack 4.17 with success?  I
was not able to finish the setup, no option to continue /add ip address. 

 

   I created a bug report here :
https://github.com/apache/cloudstack/issues/6479

 

Regards,

Cristian