[
https://issues.apache.org/jira/browse/CLOUDSTACK-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630424#comment-15630424
]
ASF GitHub Bot commented on CLOUDSTACK-9509:
--------------------------------------------
Github user nathanejohnson commented on the issue:
https://github.com/apache/cloudstack/pull/1694
@rhtyd It appears that rolling this forward to 4.9 et al has broken builds.
The signature of the CreateStoragePool constructor changed between 4.8 and 4.9.
https://github.com/apache/cloudstack/blob/4.8/server/src/com/cloud/storage/listener/StoragePoolMonitor.java#L52
That's the 4.8 version
https://github.com/apache/cloudstack/blob/4.9/server/src/com/cloud/storage/listener/StoragePoolMonitor.java#L57
That's the 4.9 version, which takes 3 parameters. When building I get the
following error:
[ERROR] <snip>
/server/test/com/cloud/storage/listener/StoragePoolMonitorTest.java:[49,29]
error: constructor StoragePoolMonitor in class StoragePoolMonitor cannot be
applied to given types;
> 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)
