[
https://issues.apache.org/jira/browse/CLOUDSTACK-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174279#comment-16174279
]
ASF subversion and git services commented on CLOUDSTACK-8865:
-------------------------------------------------------------
Commit c670691bfb82b31429d6c240290e521ec99b2b4b in cloudstack's branch
refs/heads/master from [~sudharmaj]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=c670691 ]
CLOUDSTACK-8865: Adding SR doesn't create Storage_pool_host_ref entry for
disabled host (#876)
This causes VM deployment failure on the host that was disabled while adding
the storage repository.
In the attachCluster function of the PrimaryDataStoreLifeCycle, we were only
selecting hosts that are up and are in enabled state. Here if we select all up
hosts, it will populate the DB properly and will fix this issue. Also added a
unit test for attachCluster function.
> Adding SR doesn't create Storage_pool_host_ref entry for disabled host
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-8865
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8865
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.5.0
> Reporter: sudharma jain
>
> When we add Primary Storage into XS cluster which has a host in disabled
> state the mapping info about each host and each storage pool on
> storage_pool_host_ref is not created for the disabled host. However from XS
> side SR is added in the pool elvel so SR can be seen from all hosts. James
> wants mapping info populated in db.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
