cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anshul Gangwar (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (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.
Date Mon, 08 Sep 2014 04:40:28 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anshul Gangwar reassigned CLOUDSTACK-6898:
------------------------------------------

    Assignee: Anshul Gangwar  (was: Devdeep Singh)

> [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
>            Assignee: Anshul Gangwar
>            Priority: Critical
>              Labels: hyper-V,, hyper-v, hyperv
>             Fix For: 4.4.0
>
>         Attachments: CS-6898.jpg
>
>
> 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.3.4#6332)

Mime
View raw message