You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nux (JIRA)" <ji...@apache.org> on 2014/02/17 13:01:28 UTC

[jira] [Closed] (CLOUDSTACK-6121) Putting primary storage in maintenance mode does not shut down the VMs

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

Nux closed CLOUDSTACK-6121.
---------------------------

    Resolution: Not A Problem

Thanks for clarifying!

> Putting primary storage in maintenance mode does not shut down the VMs
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6121
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6121
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM, Storage Controller, SystemVM
>    Affects Versions: 4.3.0
>         Environment: CentOS 6.5, KVM, NFS
>            Reporter: Nux
>              Labels: console, kvm, maintenance, primary, storage, systemvm
>
> According to the docs, when putting the primary storage in maintenance mode all the VMs hosted on it shut be shutdown.
> This does not happen in reality, the console proxy VM seems to be the only one that gets shut down but then it triggers a series of errors like:
> 2014-02-14 21:32:29,269 WARN  [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-5bc8688f) Exception while trying to start console proxy
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-1-VM]Scope=interface com.cloud.dc.DataCenter; id=1
>  (more here http://fpaste.org/77417/41354413/ )
> It all gets stuck because of the system vm. `virsh list` is showing the other VMs running just fine.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)