cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8601) VMFS storage added as local storage can be re added as shared storage.
Date Fri, 04 Sep 2015 18:39:46 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731218#comment-14731218
] 

ASF GitHub Bot commented on CLOUDSTACK-8601:
--------------------------------------------

Github user mike-tutkowski commented on the pull request:

    https://github.com/apache/cloudstack/pull/547#issuecomment-137815613
  
    OK, I mainly remembered the issue correctly, but not entirely. The way we avoid this problem
(usually) is by looking to see if the datastore starts with "-iqn." or "_iqn.".
    
    If it does, we assume it is not local storage; otherwise, it is assumed to be local storage
(an incorrect assumption in this situation that leads to shared storage (that has already
been added to CS as shared primary storage) being added to CS as local primary storage).


> 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)

Mime
View raw message