cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Bergsma (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-8933) SSVm and CPVM do not survice a reboot from API
Date Mon, 05 Oct 2015 21:39:27 GMT
Remi Bergsma created CLOUDSTACK-8933:

             Summary: SSVm and CPVM do not survice a reboot from API
                 Key: CLOUDSTACK-8933
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: SystemVM
    Affects Versions: 4.6.0
         Environment: KVM Advanced / Basic zone
            Reporter: Remi Bergsma
            Priority: Blocker
             Fix For: 4.6.0

These tests fail:
-          integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm
-          integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm

Stopping works, then CloudStack successfully deploys a new one. Rebooting doesn’t work as
it doesn’t complete the boot sequence. Looking at the agent.log I noticed the systemvm doesn’t
get patched so it is probably waiting for that to happen.

A successful start shows this:
2015-10-05 21:26:12,748 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Executing: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/ -n v-1-VM
-p %template=domP%type=consoleproxy%host=
2015-10-05 21:26:12,777 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Execution is successful.

The reboot doesn’t do this. When I hit reboot and run this command manually, it works:

/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/ -n v-1-VM -p %template=domP%type=consoleproxy%host=

I basically copy/pasted the patch line from the stop/start and used it when rebooting. Now
everything works.

We need to figure out why it doesn’t patch the system vms on reboot.

This message was sent by Atlassian JIRA

View raw message