[
https://issues.apache.org/jira/browse/CLOUDSTACK-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-5420:
----------------------------------
Priority: Critical (was: Major)
Marking it as Critical. Host remains in prepareForMaintenance state. If admin
wants to delete the host from CS, the only way is to change the state in DB to
Maintenance.
This bug needs a fix as early as possible as this is blocking several test
cases execution.
> Hyper-V host does not transition to maintenance mode
> ----------------------------------------------------
>
> Key: CLOUDSTACK-5420
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5420
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
> Affects Versions: 4.3.0
> Reporter: Donal Lafferty
> Assignee: Devdeep Singh
> Priority: Critical
>
> I'm trying to remove a zone, because the networking API calls did not work
> properly.
> The first step to removing the Hyper-V cluster is to remove its hosts. This
> requires they be put into maintenance mode. However, the transition to
> maintenance mode never completes.
> Can't see any exceptions in the vmops.log file, and the MaintainCommand on
> the agent does not complain. E.g.
> 2013-12-09 05:00:54,200 [25] INFO HypervResource.HypervResourceController
> [3fba50e8-fcc5-4e80-88b8-105521336c9e] - com.cloud.agent.api.MaintainCommand{
> "contextMap": {},
> "wait": 0
> }
> 2013-12-09 05:00:54,201 [25] INFO HypervResource.HypervResourceController
> [3fba50e8-fcc5-4e80-88b8-105521336c9e] - {
> "com.cloud.agent.api.MaintainAnswer": {
> "result": true,
> "details": "success - NOP for MaintainCommand",
> "_reconnect": false,
> "contextMap": {}
> }
> }
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
