[ https://issues.apache.org/jira/browse/CLOUDSTACK-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681041#comment-14681041 ]
ASF subversion and git services commented on CLOUDSTACK-8601: ------------------------------------------------------------- Commit 13a98dd196c8b0f86e4fb68db357df41767535f9 in cloudstack's branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13a98dd ] CLOUDSTACK-8601. VMFS storage added as local storage can be re-added as shared storage. Fail addition of a VMFS shared storage pool in case it has already been added as local storage in CS. > VMFS storage added as local storage can be re added as shared storage. > ---------------------------------------------------------------------- > > Key: CLOUDSTACK-8601 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8601 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Likitha Shetty > Assignee: Likitha Shetty > Fix For: 4.6.0 > > > During host discovery, if local storage is enabled for a zone, all VMFS > datastores that are mounted on just one host (i.e. not shared) will be added > as local storage is CloudStack. > When admin adds a VMFS datastore as shared, CS doesn't verify if the storage > has already been added as local storage in the zone. This means the same > primary storage is added as different storages in CS and this leads to > failure in operations related to disks because of wrong storage look ups. -- This message was sent by Atlassian JIRA (v6.3.4#6332)