Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 12 Jun 2014 10:54:01 +0000 (UTC)
From: "Abhinav Roy (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12720835.1402570381321.116465.1402570441925@arcas>
In-Reply-To: <JIRA.12720835.1402570381321@arcas>
References: <JIRA.12720835.1402570381321@arcas>
Subject: [jira] [Created] (CLOUDSTACK-6898) [Hyper-V] Open the console of a
 VM from CS, reboot the VM ( from CS or from inside the console), the
 console gets stuck at a point.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Abhinav Roy created CLOUDSTACK-6898:
---------------------------------------

             Summary: [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point.
                 Key: CLOUDSTACK-6898
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6898
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.4.0
         Environment: Hyper-V
            Reporter: Abhinav Roy
            Priority: Critical
             Fix For: 4.4.0


Steps :
==============
1. Deploy a Hyper-V setup with advanced zone.
2. Deploy a VM.
3. Now open the console of the VM from CS UI.
4. Now reboot the VM from CS or from inside the console of VM

Expected behavior :
===============
1. The console should be accessible when the the VM is rebooting and after it boots up.

Observed behavior :
==============
The console gets stuck at the point of stopping the VM and remains in that state.
Even if you close the console and reopen , it remains in the same state.
Attaching a screenshot for that.


Workaround :
============
Either close the console or even in the open state don't do any activity on it for 3 mins. After that it becomes accessible again.


--
This message was sent by Atlassian JIRA
(v6.2#6252)