Hello, The user does not receive confirmation of the operation. >From the point of view of user input it looks like the machine itself stopped.
As you can see in the logs, the ACS explicitly sends stop command, as if they press the Stop button from the GUI, so it is aware of the action from the perspective of the ACS / MS. I can not point out which component may be responsible for it. We have tried to analyze the code to understand what is happening, but the part of the code related to HAWorker is not very clear. Unfortunately we could not find online any assumptions on the level of architecture / design of HAWorker. Maybe method of small steps help find a solution. First a small question: why HAWorker performs reschedule. What was the idea for such action. 2014-07-15 14:26 GMT+02:00 Daan Hoogland <daan.hoogl...@gmail.com>: > Tomasz, > > As I understand the issue this is what happens: > > The user stops the vm from the UI > The MS sends the stop command to the machine > The machine stops and takes a long time for it > The MS reschedules the stop > Then machine stops > the user starts the machine > the MS get by stopping the machine > > Did the user ever get a confirmation that the machine was stopped or > that stopping failed? If so, this is the bug, as it seems the MS works > as designed. > > Don't get me wrong; I am trying to figure out a path to a solution for > you. I am not convinced there is a bug in the management server > though. That doesn't mean it can be in cloudstack over all. Either at > a design level or for instance in some inter-process communication. > > kind regards, > Daan Hoogland > > > On Fri, Jul 11, 2014 at 2:45 PM, Tomasz Zięba <t.a.zi...@gmail.com> wrote: > > Hello, > > > > We are waiting for the patch with longingly. > > > > Error associated with self-closing of machines causes very serious > > complications, both from the technical (users need to wait for 10 minutes > > and check if the machine is not closed automatically) as well as the > > business side (this problem does not look very professional from the user > > side) > > > > Given that: > > - An error has been detected in February so 5 months ago, > > - in earlier versions (3.0.2) error does not exists, > > - there is a procedure to reproduce this error, > > > > we would be very grateful if this issue will be resolved in ACS4.4. > > > > > > -- > > Regards, > > Tomasz Zięba > > Twitter: @TZieba > > LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/ > <http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/> > > > > 2014-07-11 13:48 GMT+02:00 Daan Hoogland <daan.hoogl...@gmail.com>: > > > >> Our beloved VP pointed out that there has not come a vote conclusion > yet: > >> > >> The 4.4.0 vote has resulted in a rejection of the present release > >> candidate due to -1 of Marcus and no active voting since. > >> > >> there are three issues pending from this vote thread: > >> - CLOUDSTACK-6036 (Tomasz) > >> - unable to add a KVM host (Marcus) > >> - top level pom.xml still contains a -SNAPSHOT suffix (Ove, question > >> outstanding to Tim) > >> > >> Can I have some reporting on the status of those issues by the > >> reporters, please? > >> > >> regards, > >> your friendly release manager > >> > >> > >> On Wed, Jul 2, 2014 at 10:18 PM, Daan Hoogland <daan.hoogl...@gmail.com > > > >> wrote: > >> > Hi All, > >> > > >> > I've created a 4.4.0 release, with the following artifacts up for a > >> > vote: > >> > > >> > Git Branch and Commit SH: > >> > > >> > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.4-RC20140702T2107 > >> > Commit: 379387961bd05d1f84fe2e9a1997e9ecdceef91a > >> > > >> > List of changes: > >> > > >> > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/ > >> > > >> > Source release (checksums and signatures are available at the same > >> > location): > >> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.0/ > >> > > >> > PGP release keys (signed using 4096R/AA4736F3): > >> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > >> > > >> > Vote will be open for 72 hours. > >> > > >> > For sanity in tallying the vote, can PMC members please be sure to > >> > indicate "(binding)" with their vote? > >> > > >> > [ ] +1 approve > >> > [ ] +0 no opinion > >> > [ ] -1 disapprove (and reason why) > >> > > >> > > >> > I will ad my key to the mentioned KEYS file as soon as possible, > >> > -- > >> > Daan > >> > >> > >> > >> -- > >> Daan > > > > > > > > > > -- > Daan > -- Regards, Tomasz Zięba Twitter: @TZieba LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/ <http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>
