re-download systemvm template

Discussion:

Sonali Jadhav

2015-07-20 06:09:36 UTC

Hi

I am running ACS 4.5.1. I want to re-download systemvm template, I am not able to create new network VR . Template I used is from http://cloudstack.apt-get.eu and I saw last week a thread about using new templates from shapeblue. How I can re-download it? I can't delete it, coz it says "The DomR template cannot be deleted".

Recent changes: Upgraded from 4.4.2 to 4.5.1. Other VMs and VR are working fine. Even I am able to create new instance form existing VR. But not able to create new network. So I suspect some issue in template.
Also all VRs and System VMs are showing version 4.5.0.

My current template status is Ready. But still I get this weird issue of invalid uuid exception, when it creates new VR. Following is xensource logs, (copy in notepad and search for "invalid" word, you'll know better)

Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.set_name_label R:ab99932e0fdb|mscgen] xapi=>xapi [label="(XML)"];
Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448830 UNIX /var/xapi/xapi||dummytaskhelper] task dispatch:session.logout D:c17496b43467 created by task R:ab99932e0fdb
Jul 16 13:28:03 SeSolXS01 xapi: [ info|SeSolXS01|2448830 UNIX /var/xapi/xapi|session.logout D:4765ab28a40d|xapi] Session.destroy trackid=972a882b68efc06b18265d6e28939b95
Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.create R:d044ac329873|audit] VM.create: name_label = 'r-114-VM' name_description = 'Template that allows VM installation from Xen-aware Debian-based distros. To use this template from the CLI, install your VM using vm-install, then set other-config-install-repository to the path to your network repository, e.g. http://<server>/<path>'
Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VM.set_VCPUs_params D:74bfb6d0f66a|api_effect] VM.set_VCPUs_params
Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VM.set_PV_args D:6bb8f68bca3f|api_effect] VM.set_PV_args
Jul 16 13:28:03 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VM.set_PV_bootloader D:61cdaa44a24c|api_effect] VM.set_PV_bootloader
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VM.set_platform D:d36fe147d78b|api_effect] VM.set_platform
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:6ca3340dcd7d|audit] VBD.create: VM = '342ff291-edad-33e6-ab6a-263fe14f867f (r-114-VM)'; VDI = '9c6aaeb7-2d43-4cf4-a7b0-42d0b107295e'
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:6ca3340dcd7d|xapi] Checking whether there's a migrate in progress...
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:6ca3340dcd7d|xapi] VBD.create (device = 0; uuid = 83e9358a-0d6d-9b59-80a3-ad191e95d08f; ref = OpaqueRef:fef6fe16-a920-3ad9-8ee1-004aba61357c)
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:a9db96f22f30|audit] VBD.create: VM = '342ff291-edad-33e6-ab6a-263fe14f867f (r-114-VM)'; VDI = 'invalid'
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:a9db96f22f30|xapi] Checking whether there's a migrate in progress...
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.create R:a9db96f22f30|xapi] VBD.create (device = 3; uuid = 965b4746-8444-a7f3-5b49-2a755f0468c9; ref = OpaqueRef:b0678a49-13a2-ff03-7525-66c4c38efb77)
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|backtrace] Raised at db_cache_impl.ml:198.16-55 -> db_actions.ml:13331.27-61 -> rbac.ml:229.16-23 -> rbac.ml:238.10-15 -> server_helpers.ml:76.11-23
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|dispatcher] Server_helpers.exec exception_handler: Got exception UUID_INVALID: [ VDI; 01f00c56-10ac-42b3-ab99-67bfb26e88ba ]
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VDI.get_by_uuid D:c3451d9e93fa|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VDI.get_by_uuid D:8b7e8b115487|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|dispatch:VDI.get_by_uuid D:8b7e8b115487|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:140.10-106 -> server.ml:22425.23-183 -> server_helpers.ml:119.4-7
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.destroy R:c1058c9b591c|audit] VM.destroy: VM = '342ff291-edad-33e6-ab6a-263fe14f867f (r-114-VM)'
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.destroy R:c1058c9b591c|mscgen] xapi=>xcp-rrdd [label="remove_rrd"];
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.destroy R:c1058c9b591c|xapi] VM.destroy: deleting DB records
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.destroy R:c1058c9b591c|xapi] Raised at db_cache_types.ml:107.27-69 -> db_cache_impl.ml:153.11-44 -> pervasiveext.ml:22.2-9
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VM.destroy R:c1058c9b591c|xapi] Raised at db_cache_types.ml:107.27-69 -> db_cache_impl.ml:240.11-44 -> pervasiveext.ml:22.2-9
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|audit] VBD.unplug: VBD = 'invalid'
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|backtrace] Raised at db_cache_types.ml:107.27-69 -> db_cache_impl.ml:129.11-44 -> db_actions.ml:14033.43-72 -> xapi_vbd_helpers.ml:206.12-55 -> message_forwarding.ml:3431.5-65 -> message_forwarding.ml:283.5-8
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|xapi] Caught exception while HANDLE_INVALID: [ VBD; OpaqueRef:b0678a49-13a2-ff03-7525-66c4c38efb77 ] in message forwarder: marking VBD for VBD.unplug
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|backtrace] Raised at message_forwarding.ml:286.8-9 -> threadext.ml:20.20-24 -> threadext.ml:20.62-65 -> message_forwarding.ml:149.19-25 -> message_forwarding.ml:3436.3-87 -> message_forwarding.ml:3512.3-200 -> rbac.ml:229.16-23
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|backtrace] Raised at rbac.ml:238.10-15 -> server_helpers.ml:79.11-41
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|dispatcher] Server_helpers.exec exception_handler: Got exception HANDLE_INVALID: [ VBD; OpaqueRef:b0678a49-13a2-ff03-7525-66c4c38efb77 ]
Jul 16 13:28:04 SeSolXS01 xapi: [debug|SeSolXS01|2448722 INET :::80|VBD.unplug R:5332760ab48b|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29

Stephan Seitz

2015-07-20 08:16:28 UTC

Permalink

Hi,

if you carefully followed the upgrade-docs [1], recent systemvm versions
should spawn if you destroy the current ones.
A slightly better way is using the documented "cloudstack-sysvmadm"
command for upgrading the systemvn.

If you want to use particular templates for different kinds of systemvm,
navigate to the Settings menu and search for "template". You'll be able
to change e.g. router.template.xenserver to the *Name* (as seen in the
Templates Menu) of your specific template.

Anyway, If - after an update which followed 100% the documentation - the
setup of new systemvm (or at least virtual routers) fails, you'll have
to dig deeper into your logs (don't miss the logs from inside the
running routervms) to get a clue whats happened.

cheers,

Stephan

[1]
http://cloudstack-release-notes.readthedocs.org/en/4.5.1/upgrade/upgrade-4.4.html

Post by Sonali Jadhav
Hi
I am running ACS 4.5.1. I want to re-download systemvm template, I am not able to create new network VR . Template I used is from http://cloudstack.apt-get.eu and I saw last week a thread about using new templates from shapeblue. How I can re-download it? I can't delete it, coz it says "The DomR template cannot be deleted".
Recent changes: Upgraded from 4.4.2 to 4.5.1. Other VMs and VR are working fine. Even I am able to create new instance form existing VR. But not able to create new network. So I suspect some issue in template.
Also all VRs and System VMs are showing version 4.5.0.

Sonali Jadhav

2015-07-20 09:03:18 UTC

Permalink

Yes I have followed 100% upgrade guides, with no problems. And I want to re-download template, like I said before existing VRs and system VMs don't have any problem they are upgrade to 4.5, as I can see their version in acs. So cloudstack-sysvmadm is not what I am looking for.

I am having problem creating new network, I dig up more and I found that there are two API calls for creating VBD for one VR. One with valid UUID number and 2nd one is blank ? and that's what causing this invalid uuid exception.

This is what I saw in XenServer audit logs,

Jul 20 09:44:20 SeSolXS01 xapi: [20150720T07:44:20.828Z|audit|SeSolXS01|3347500 INET :::80|VBD.create R:d73a9219fc0c|audit] ('trackid=b38fe90608f537ee8125aee0fdc66c2f' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM' 'r-118-VM' '1a85ce50-b4d5-c08c-8e0e-f0f8d6a59d79' 'OpaqueRef:4ba05d7c-f5a1-bb92-5734-a2180ca2c52f') ('VDI' 'ROOT-118' 'b9b2c03c-759a-4320-a723-7f7c4f5265a5' 'OpaqueRef:e0078cc8-34f1-c608-596c-911e5cc3a83f') ('metrics' '' '' 'OpaqueRef:NULL')))

Jul 20 09:44:20 SeSolXS01 xapi: [20150720T07:44:20.879Z|audit|SeSolXS01|3347500 INET :::80|VBD.create R:581f0e4ce003|audit] ('trackid=b38fe90608f537ee8125aee0fdc66c2f' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM' 'r-118-VM' '1a85ce50-b4d5-c08c-8e0e-f0f8d6a59d79' 'OpaqueRef:4ba05d7c-f5a1-bb92-5734-a2180ca2c52f') ('VDI' '' '' 'OpaqueRef:NULL') ('metrics' '' '' 'OpaqueRef:NULL')))

I don't know , if this is how it should be ? I mean blank VDI uuid in API call ? I want to understand what's happening.

/Sonali

-----Original Message-----
From: Stephan Seitz [mailto:***@secretresearchfacility.com]
Sent: Monday, July 20, 2015 1:46 PM
To: ***@cloudstack.apache.org
Subject: Re: re-download systemvm template

Hi,

if you carefully followed the upgrade-docs [1], recent systemvm versions should spawn if you destroy the current ones.
A slightly better way is using the documented "cloudstack-sysvmadm"
command for upgrading the systemvn.

If you want to use particular templates for different kinds of systemvm, navigate to the Settings menu and search for "template". You'll be able to change e.g. router.template.xenserver to the *Name* (as seen in the Templates Menu) of your specific template.

Anyway, If - after an update which followed 100% the documentation - the setup of new systemvm (or at least virtual routers) fails, you'll have to dig deeper into your logs (don't miss the logs from inside the running routervms) to get a clue whats happened.

cheers,

Stephan

[1]
http://cloudstack-release-notes.readthedocs.org/en/4.5.1/upgrade/upgrade-4.4.html

Pierre-Luc Dion

2015-07-20 11:37:09 UTC

Permalink

Sonali,

One thing you could try is the instruction from the following release
note[1] but use the latest systemvm template for 4.5.1? if you download the
new template, once the download is complete
you would need to change the Global Settings: router.template.xen to the
name of the new template. if you don't need to update SSVM,CPVM, forget the
SQL changes.

Then, restart networks or VPCs to force a reinstallation of the VRs.

[1]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.0/upgrade/upgrade-4.3.html#manual-hotfix-for-systemvm-upgrade

Post by Sonali Jadhav
Yes I have followed 100% upgrade guides, with no problems. And I want to
re-download template, like I said before existing VRs and system VMs don't
have any problem they are upgrade to 4.5, as I can see their version in
acs. So cloudstack-sysvmadm is not what I am looking for.
I am having problem creating new network, I dig up more and I found that
there are two API calls for creating VBD for one VR. One with valid UUID
number and 2nd one is blank ? and that's what causing this invalid uuid
exception.
This is what I saw in XenServer audit logs,
[20150720T07:44:20.828Z|audit|SeSolXS01|3347500 INET :::80|VBD.create
R:d73a9219fc0c|audit] ('trackid=b38fe90608f537ee8125aee0fdc66c2f'
'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM'
'r-118-VM' '1a85ce50-b4d5-c08c-8e0e-f0f8d6a59d79'
'OpaqueRef:4ba05d7c-f5a1-bb92-5734-a2180ca2c52f') ('VDI' 'ROOT-118'
'b9b2c03c-759a-4320-a723-7f7c4f5265a5'
'OpaqueRef:e0078cc8-34f1-c608-596c-911e5cc3a83f') ('metrics' '' ''
'OpaqueRef:NULL')))
[20150720T07:44:20.879Z|audit|SeSolXS01|3347500 INET :::80|VBD.create
R:581f0e4ce003|audit] ('trackid=b38fe90608f537ee8125aee0fdc66c2f'
'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'VBD.create' (('VM'
'r-118-VM' '1a85ce50-b4d5-c08c-8e0e-f0f8d6a59d79'
'OpaqueRef:4ba05d7c-f5a1-bb92-5734-a2180ca2c52f') ('VDI' '' ''
'OpaqueRef:NULL') ('metrics' '' '' 'OpaqueRef:NULL')))
I don't know , if this is how it should be ? I mean blank VDI uuid in API
call ? I want to understand what's happening.
/Sonali
-----Original Message-----
Sent: Monday, July 20, 2015 1:46 PM
Subject: Re: re-download systemvm template
Hi,
if you carefully followed the upgrade-docs [1], recent systemvm versions
should spawn if you destroy the current ones.
A slightly better way is using the documented "cloudstack-sysvmadm"
command for upgrading the systemvn.
If you want to use particular templates for different kinds of systemvm,
navigate to the Settings menu and search for "template". You'll be able to
change e.g. router.template.xenserver to the *Name* (as seen in the
Templates Menu) of your specific template.
Anyway, If - after an update which followed 100% the documentation - the
setup of new systemvm (or at least virtual routers) fails, you'll have to
dig deeper into your logs (don't miss the logs from inside the running
routervms) to get a clue whats happened.
cheers,
Stephan
[1]
http://cloudstack-release-notes.readthedocs.org/en/4.5.1/upgrade/upgrade-4.4.html

Post by Sonali Jadhav
Hi
I am running ACS 4.5.1. I want to re-download systemvm template, I am

not able to create new network VR . Template I used is from
http://cloudstack.apt-get.eu and I saw last week a thread about using new
templates from shapeblue. How I can re-download it? I can't delete it, coz
it says "The DomR template cannot be deleted".

Post by Sonali Jadhav
Recent changes: Upgraded from 4.4.2 to 4.5.1. Other VMs and VR are

working fine. Even I am able to create new instance form existing VR. But
not able to create new network. So I suspect some issue in template.

Post by Sonali Jadhav
Also all VRs and System VMs are showing version 4.5.0.