[
https://issues.apache.org/jira/browse/CLOUDSTACK-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631479#comment-15631479
]
ASF GitHub Bot commented on CLOUDSTACK-9509:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1694
@nathanejohnson I'm not sure what you are doing, the build failure was due
to a unit test introduced in this PR. In 4.9+ branches, the unit test did not
consider the additional parameter added to the constructor signature in 4.9+
branches. The simplest fix was to simply pass null, as the unit test does not
depend/use that additional parameter. Thanks for bringing this to my attention,
the build is fixed on 4.9, master branches now.
> KVM Hosts connect with no storage
> ---------------------------------
>
> Key: CLOUDSTACK-9509
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9509
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Priority: Critical
> Fix For: 4.8.1, 4.10.0.0, 4.9.1.0
>
>
> KVM hosts on shared storage failure was accepted by mgmt server with the
> host state as Up, even though there was no primary/shared storage available
> on it. They fail the ModifyStoragePoolCommand, but the management server
> continues on with adding SSH keys and marking them as up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
