cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Young <iyo...@ratespecial.com>
Subject Re: upgraded to 4.4.1, management console is broken
Date Fri, 03 Oct 2014 20:51:47 GMT
It looks like this is the root of the problem:

2014-10-03 13:44:47,131 DEBUG [c.c.u.d.Upgrade440to441] (main:null)
Updating System Vm template IDs
2014-10-03 13:44:47,136 DEBUG [c.c.u.d.Upgrade440to441] (main:null)
Updating LXC System Vms
2014-10-03 13:44:47,137 WARN  [c.c.u.d.Upgrade440to441] (main:null) 4.4.0
LXC SystemVm template not found. LXC hypervisor is not used, so not failing
upgrade
2014-10-03 13:44:47,138 DEBUG [c.c.u.d.Upgrade440to441] (main:null)
Updating KVM System Vms
2014-10-03 13:44:47,141 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: 4.4.0 KVM SystemVm
template not found. Cannot upgrade system Vms

Any ideas about how I can fix this?  I had a 4.4.0 KVM SystemVm template
prior to the upgrade.

On Fri, Oct 3, 2014 at 1:39 PM, Ian Young <iyoung@ratespecial.com> wrote:

> I tried upgrading from 4.4.0 to 4.4.1 but now I get a 404 error when I try
> to access the management console.  The localhost.2014-10-03.log shows this
> error:
>
> Caused by: java.io.IOException: Resource
> [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-api-4.4.1.jar!/META-INF/cloudstack/api-config/module.properties]
> and
> [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-api-4.4.0.jar!/META-INF/cloudstack/api-config/module.properties]
> do not appear to be the same resource, please ensure the name property is
> correct or that the module is not defined twice
>
> Where is this value defined?  The full log can be viewed here:
>
> pastebin.com/nrdEsxZK
>
> I also noticed the error "4.4.0 KVM SystemVm template not found. Cannot
> upgrade system Vms."  The URL for the system VM template in the 4.4.1
> upgrade instructions is the same as the one I used when I installed 4.4.0
> initially.  Is there really a need to install the same template again?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message