Jevgeni, if your KVM host/agent is Up, use the provisionCertificate API or in the UI goto Infra > Hosts > the KVM host where the issue is seen > click the third button from the left that says 'provision host security keys'. This will re-provision the key and restart libvirtd.
In case the KVM host agent is unable to join as well due to key/cert error, set the global setting ca.plugin.root.auth.strictness to false, wait for all KVM agents to be Up, then set the global setting back to true and re-provision host keys (using the API or UI). Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com ________________________________ From: Jevgeni Zolotarjov <[email protected]> Sent: Thursday, July 4, 2019 2:28:37 PM To: [email protected] Subject: Re: failure after update 4.11.2 -> 4.11.3 I downgraded cloudstack to 4.11.2 But apparently as the result of previous update libvirtd got updated. Now it does not start with following error: ---------------------------------------------------------------------------------------------------------------------------------------------------------------- 2019-07-04 08:39:43.761+0000: 27030: error : virNetTLSContextLoadCredentials:671 : Unable to set x509 key and certificate: /etc/pki/libvirt/private/serverkey.pem, /etc/pki/libvirt/servercert.pem: The provided X.509 certificate list is not sorted (in subject to issuer order) ------------------------------------------------------------------------------------------------------------------------------------ How to resolve this problem? On Thu, Jul 4, 2019 at 11:20 AM Rohit Yadav <[email protected]> wrote: > Hi Jevgeni, > > > We're yet to update the release notes, fix the upgrade docs and announce > the release which my colleague and RM Paul Angus will do soon. > > > You need to setup the 4.11.3 systemvmtemplate and use the name/version > suffix was `-4.11.3` while registering the template before the upgrade. ( > http://docs.cloudstack.apache.org/en/4.11.2.0/upgrading/upgrade/upgrade-4.11.html > ) > > > Then use one of the upstream packages, link of which was shared on dev@ > to upgrade. > > > Since you've already upgraded, you can downgrade the package to 4.11.2.0 > and remove the 4.11.3.0 version row in the cloud.version table. And then > restart the management server. Then retry the systemvmtemplate (4.11.3) > registration and upgrade to the available packages (as mentioned, we're yet > to fix the notes and links). > > > Regards, > > Rohit Yadav > > Software Architect, ShapeBlue > > https://www.shapeblue.com > > ________________________________ > From: Jevgeni Zolotarjov <[email protected]> > Sent: Thursday, July 4, 2019 11:40:16 AM > To: [email protected] > Subject: failure after update 4.11.2 -> 4.11.3 > > Hello > > I followed installation steps as described here > > http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.11.htm > > I made sure, that system VM templates were in READY state. > > But after update management server does not start > ● cloudstack-management.service - CloudStack Management Server > Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled; vendor preset: disabled) > Active: active (running) since Thu 2019-07-04 06:00:45 GMT; 14s ago > Main PID: 13166 (java) > Tasks: 62 > CGroup: /system.slice/cloudstack-management.service > └─13166 /usr/bin/java > -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers > -Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2G > -XX:+HeapDumpOnOutOfMemoryErr... > > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: at > > org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: ... 47 more > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: Caused by: > com.cloud.utils.exception.CloudRuntimeException: 4.11.3.0KVM SystemVm > template not found. Cannot upgrade system Vms > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: at > > com.cloud.upgrade.dao.Upgrade41120to41130.updateSystemVmTemplates(Upgrade41120to41130.java:203) > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: at > > com.cloud.upgrade.dao.Upgrade41120to41130.performDataMigration(Upgrade41120to41130.java:60) > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: at > > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:586) > Jul 04 06:00:59 mtl1-apphst03.mt.pbt.com.mt java[13166]: ... 49 more > > > How to fix this problem? > > [email protected] > www.shapeblue.com<http://www.shapeblue.com> > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > [email protected] www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
