[
https://issues.apache.org/jira/browse/CLOUDSTACK-9676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772749#comment-15772749
]
ASF subversion and git services commented on CLOUDSTACK-9676:
-------------------------------------------------------------
Commit 20986ba51215b75c67b0c4035d55a27c3de313d1 in cloudstack's branch
refs/heads/4.9 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20986ba ]
Merge pull request #1854 from shapeblue/4.9-multiplex-testing
4.9 multiplex testingThis merges several PRs in this PR, this is for speeding
up test efforts.
* pr/1854:
CLOUDSTACK-9688: Fix VR smoke test failure in vpc_vpn
CLOUDSTACK-9688: Fix failing test_volumes on centos7/kvm
CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when
there are child VM snapshots
CLOUDSTACK-9612: Fixed issue in restarting redundant network with cleanup Rvr
Network with cleanup which is updated from the isolated network is failed.
Corrected the column name string issue.
CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when
there are child VM snapshots
CLOUDSTACK-9673 Exception occured while creating the CPVM in the VmWare Setup
over standard vSwitches
CLOUDSTACK-9617: Fixed enabling remote access after PF or LB configured on
vpn tcp ports
CLOUDSTACK-9615: Fixed applying ingress rules without ports
CLOUDSTACK-9639: Unable to create shared network with vLan isolation
CLOUDSTACK-9597: Should not fetch resource count for removed entity
CLOUDSTACK-9649: In the management server log there is an error related to
0.0.0.0 IP address
Signed-off-by: Rohit Yadav <[email protected]>
> Start instance fails after reverting to a VM snapshot, when there are child
> VM snapshots
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9676
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9676
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.9.0.1
> Environment: vSphere 5.5
> ACS master commit 17653a86fad67447a4f13e455e336694ad5c1735
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.10.0.0
>
>
> Start instance fails after reverting to a VM snapshot, when there is 1 or
> more child VM snapshots in the snapshot tree of the VM.
> Per the code that detects the presence of a snapshot, we are checking for
> only current snapshot instead of checking presence of any snapshot in the
> snapshot tree. The failure to detect all snapshots means ACP reconfigures the
> VM in wrong way assuming there are no snapshots for the VM. This results in
> start failure.
> {code:borderStyle=solid}
> public boolean hasSnapshot() throws Exception {
> VirtualMachineSnapshotInfo info = getSnapshotInfo();
> if (info != null) {
> return info.getCurrentSnapshot() != null;
> }
> return false;
> }
> {code}
> Steps to reproduce
> ===============
> # Prepare setup with esxi5.5
> # Deploy a vm and create three snapshot i1,i2,i3.
> # Delete i2. and stop vm
> # Revert vm to i1
> # Delete i1
> # Start vm
> Start vm is failing with error,
> {noformat}
> StartCommand failed due to Exception: java.lang.RuntimeException Message:
> Invalid configuration for device '0'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
