cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9046) Fix upgrade path from 4.4 and 4.5 to 4.6
Date Mon, 09 Nov 2015 14:35:11 GMT


ASF GitHub Bot commented on CLOUDSTACK-9046:

GitHub user wilderrodrigues opened a pull request:

    CLOUDSTACK-9046 - Fix upgrade path from 4.4 and 4.5 to 4.6

    This PR fixes the upgrade path from 4.4.x/4.5.x to 4.6.0. We introduced the logic to update
the database with the correct information about the SystemVMs.
    We tested this PR with by doing an upgrade from 4.4.4 to 4.6.0 and it works as expected.

You can merge this pull request into a Git repository by running:

    $ git pull fix/upgrade_path-CLOUDSTACK-9046

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1050
commit 4b503b45821976ada42a4f6cdd1894caa8794505
Author: Wilder Rodrigues <>
Date:   2015-11-09T09:06:19Z

    CLOUDSTACK-9046 - Add SystemVM upgrade from 4.5 to 4.6 in the file

commit 72e79bcaa6eacc0041694120f7ea53792dc68975
Author: Wilder Rodrigues <>
Date:   2015-11-09T13:38:17Z

    CLOUDSTACK-9046 - Add new ACS systemVMs website
       - Also change the URl in the SQL file.


> Fix upgrade path from 4.4 and 4.5 to 4.6
> ----------------------------------------
>                 Key: CLOUDSTACK-9046
>                 URL:
>             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 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
>", line 20, in <module>    from merge import QueueFile  File "/opt/cloud/bin/",
line 23, in <module>    import cs_ip  File "/opt/cloud/bin/", 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

View raw message