cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Bergsma (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-8811) Hyper-V investigator returns false instead of true causing corruption
Date Fri, 04 Sep 2015 20:18:45 GMT
Remi Bergsma created CLOUDSTACK-8811:
----------------------------------------

             Summary: Hyper-V investigator returns false instead of true causing corruption
                 Key: CLOUDSTACK-8811
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8811
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.4.4
         Environment: Any hypervisor
            Reporter: Remi Bergsma
            Assignee: Remi Bergsma
            Priority: Critical
             Fix For: 4.4.5


CloudStack has many different Investigators, one for each hypervisor type. In general, it
was agreed on that these Investigators could say either 'true' aka 'yes, I confirm that VM
is running', 'false' aka 'no, I confirm that VM is for sure NOT running' or 'null' aka 'I
am unable to determine the state so please ask another Investigator'.

The Hyper-V Investigator reported 'false' instead of 'null'. In other words, it confirmed
VMs as NOT running while it should have said it couldn't tell. As a concequence, CloudStack
deprovisioned the resources. In reality the VMs were still running. You can imagine this causes
a mess.

Fixed here: https://github.com/apache/cloudstack/pull/761




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

Mime
View raw message