If you have a backup I suggest you downgrade and do it from scratch, if not you 
can do some DB hacking to fake it that the template is good to go, so it can 
carry on with the upgrade. 

If I were you, I would choose to roll-back the db and packages to 4.11.2 and do 
the upgrade again. 

Thanks,
Bobby.

On 4.07.19, 10:14, "Jevgeni Zolotarjov" <[email protected]> wrote:

    I checked that it is in READY state
    
    Anyway. What to do now?
    
    On Thu, Jul 4, 2019 at 10:03 AM Boris Stoyanov 
<[email protected]>
    wrote:
    
    > Hi Jevgeni,
    >
    > Did you made sure your 4.11.3 systemvm template is installed and usable
    > before diving into upgrade?
    >
    > Looks like cloudstack cannot find a 4.11.3 template to carry on the
    > template.
    >
    > Thanks,
    > Bobby.
    >
    > On 4.07.19, 9:10, "Jevgeni Zolotarjov" <[email protected]> wrote:
    >
    >     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
    > Amadeus House, Floral Street, London  WC2E 9DPUK
    > @shapeblue
    >
    >
    >
    >
    


[email protected] 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Reply via email to