Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 5 Nov 2014 16:27:35 +0000 (UTC)
From: "Ram Ganesh (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12687887.1389196722000.424036.1415204855769@Atlassian.JIRA>
In-Reply-To: <JIRA.12687887.1389196722000@Atlassian.JIRA>
References: <JIRA.12687887.1389196722000@Atlassian.JIRA>
 <JIRA.12687887.1389196722855@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-5836) When tried to reverting back to
 (disk attached)quiesced vm snapshot, got error at logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5836?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ram Ganesh updated CLOUDSTACK-5836:
-----------------------------------
    Fix Version/s: 4.5.0

> When tried to reverting back to (disk attached)quiesced vm snapshot, got =
error at logs
> -------------------------------------------------------------------------=
-------------
>
>                 Key: CLOUDSTACK-5836
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-583=
6
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: API, Snapshot
>    Affects Versions: 4.3.0
>         Environment: cloudstack 4.3,vm snapshot
>            Reporter: rashid
>            Assignee: edison su
>             Fix For: 4.4.0, 4.5.0
>
>
> Environment: There is a vm with attached disk. When tried to revert back =
to older vm snapshot then I saw the below error message in log &
> =E2=80=A2=09VM did not stop
> =E2=80=A2=09At notification it says =E2=80=9Csuccessfull=E2=80=9D & No GU=
I error message
> Manually powered off and powered on the vm and verified that Vm has been =
successfully reverted.
> But , why vm did not get powered off by itself?
> PLease check the below logs=20
> INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-41:ctx-5711a5dd) Add jo=
b-93 into job monitoring INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-=
42:ctx-b7e47685) Add job-94 into job monitoring INFO  [o.a.c.f.j.i.AsyncJob=
Monitor] (Job-Executor-43:ctx-7c2d7cd2) Add job-93 into job monitoring INFO=
  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-42:ctx-b7e47685) Remove job-9=
4 from job monitoring WARN  [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor=
-43:ctx-7c2d7cd2) job-93 is scheduled for wakeup run, but there is no joini=
ng info anymore ERROR [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-43:ct=
x-7c2d7cd2) Unable to find a wakeup dispatcher from the joined job: AsyncJo=
bVO {id:93, userId: 2, accountId: 2, instanceType: None, instanceId: null, =
cmd: org.apache.cloudstack.api.command.user.vmsnapshot.RevertToVMSnapshotCm=
d, cmdInfo: {"response":"json","sessionkey":"LAwQEgGPTl8PlWexb67vz8P8SoU\u0=
03d","cmdEventType":"VMSNAPSHOT.REVERTTO","ctxUserId":"2","httpmethod":"GET=
","vmsnapshotid":"4b1ea7b0-7274-4d35-bfd8-d1f151eabe3e","_":"1389095290252"=
,"ctxAccountId":"2","ctxStartEventId":"119"}, cmdVersion: 0, status: IN_PRO=
GRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 34505256503=
4, completeMsid: null, lastUpdated: null, lastPolled: null, created: Tue Ja=
n 07 06:48:10 EST 2014} INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-4=
3:ctx-7c2d7cd2) Remove job-93 from job monitoring INFO  [o.a.c.f.j.i.AsyncJ=
obMonitor] (Job-Executor-41:ctx-5711a5dd) Remove job-93 from job monitoring=
 INFO  [c.c.h.HighAvailabilityManagerImpl] (HA-2:ctx-943a466a) checking hea=
lth of usage server


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