cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9046) Fix upgrade path from 4.4 and 4.5 to 4.6
Date Mon, 09 Nov 2015 09:34:11 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996253#comment-14996253
] 

Wei Zhou commented on CLOUDSTACK-9046:
--------------------------------------

[~remibergsma] ok. I upgraded from 4.2 to 4.6 in August. I just recalled I made a database
change to make it work.
update vm_template set type='SYSTEM' where name='systemvm-kvm-4.6';
It is a critical issue indeed. 
Is Wilder working on it now? He might find a better solution for it.

> Fix upgrade path from 4.4 and 4.5 to 4.6
> ----------------------------------------
>
>                 Key: CLOUDSTACK-9046
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9046
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.6.0
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>            Priority: Blocker
>             Fix For: 4.6.0
>
>
> When upgrading to 4.6 from 4.5 or earlier, the systemvm template that is registered upfront
is not marked as SYSTEM and set as the template for the existing systemvms. Therefore, new
systemvms work fine but existing ones don't.
> RCA is missing code in the upgrade path, as is present when upgrading from 4.4 to 4.5
for example.
> The code in the Upgrade442to450.java is not generic, as the name suggests, and simply
configures the whole SystemVM and all the existing Domain VMs to use the SystemVM-4.5.0 that
was registered. It means that after the upgrade all the routers were marked okay, but they
were using the old stuff, from 4.5.0. The attempt to deploy a new VM was also failing with
the following error (on the host):
> 2015-11-07 18:17:31,135 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Exit value is 1
> 2015-11-07 18:17:31,135 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Traceback (most recent call last):  File "/opt/cloud/bin/update_con
> fig.py", line 20, in <module>    from merge import QueueFile  File "/opt/cloud/bin/merge.py",
line 23, in <module>    import cs_ip  File "/opt/cloud/bin/cs_ip.py", lin
> e 19, in <module>    from netaddr import *ImportError: No module named netaddr
> Why that? Because the KVM host has the new systemvm.iso, which contains all the new python
stuff, but the systemvm template, which installs the Guest OS (Debian) is old and does not
contain the modules we now need.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message