[
https://issues.apache.org/jira/browse/CLOUDSTACK-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856186#comment-13856186
]
Devdeep Singh commented on CLOUDSTACK-5420:
-------------------------------------------
The issue is generic and not specific to hyper-v. In commit
1d4b22d6de7f28de89e592a218343bacf7c0b2b0 the agent monitor was removed and code
moved to agent manager. However, the piece of code that transitions the host to
maintenance mode is commented out. The same issue will be observed in other
hypervisors too.
> 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)
