You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/19 08:44:00 UTC
[jira] [Commented] (CLOUDSTACK-9992) Failed to change cluster to
managed state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134025#comment-16134025 ]
ASF subversion and git services commented on CLOUDSTACK-9992:
-------------------------------------------------------------
Commit d450e1acc0f39183e910c99abbbc8e3b98f9c2b0 in cloudstack's branch refs/heads/master from [~niteshsarda]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=d450e1a ]
CLOUDSTACK-9992 : Failed to change cluster to managed state
> Failed to change cluster to managed state
> -----------------------------------------
>
> Key: CLOUDSTACK-9992
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9992
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Nitesh Sarda
>
> ISSUE
> ============
> Failed to change cluster to managed state.
> STEPS TO REPRODUCE
> ==================
> # Create an environment having zone with 2 Clusters and atleast 1 host associated with each cluster.
> # Verify that all clusters are in managed state and all hosts are in up state.
> # Change the value of global setting "direct.agent.load.size" to 1.
> # Restart management server.
> # Check "id" of both clusters.
> # Change state of bot the clusters to Unmanaged state.
> # Try to change the cluster which has higher "id" to managed state. Cluster will come to manage state.
> # But host associated with it will never come to UP state, till the time cluster with lower "id" is changed to manage state.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)