Thanks Nicolas, It is not actually the new hosts, but the old hosts that went from "up" to "unsecured".
the newly added hosts turned out fine as "up". Regards, Rafael On Fri, 2020-10-09 04:54 PM, Nicolas Vazquez <nicolas.vazq...@shapeblue.com> wrote: > Hi Rafael, > > As Rakesh mentions that can be one option, or can also provision a new > certificate to the new hosts through the CloudStack UI/API > provisionCertificate (the button should be on the hosts details tab). > > > Regards, > > Nicolas Vazquez > > ________________________________ > From: Rakesh v " target="_blank"><www.rakeshv....@gmail.com> > Sent: Friday, October 9, 2020 8:47 AM > To: users@cloudstack.apache.org " > target="_blank"><users@cloudstack.apache.org> > Subject: Re: KVM hosts transitioned from "up" to "unsecured" > > You might want to add libvirtd_opts="-l" In /etc/default/libvirt-bin > > Sent from my iPhone > > > nicolas.vazq...@shapeblue.com > http://www.shapeblue.com > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > @shapeblue > > > > > On 09-Oct-2020, at 9:18 AM, rva...@privaz.io.invalid wrote: > > > > Hi! > > > > Yesterday I added more hosts to a cluster, and the ones that were there are > > now showing as "unsecured". > > > > Probably my installation playbook messed something up. > > > > Any idea what could have triggered such a thing to happen? > > > > anybody suffered this also? > > > > Rafael >
