You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/06/29 09:00:22 UTC

[jira] [Created] (CLOUDSTACK-3289) StorageSubsystem: cannot add image store of a different provider in a different zone

Prasanna Santhanam created CLOUDSTACK-3289:
----------------------------------------------

             Summary: StorageSubsystem: cannot add image store of a different provider in a different zone
                 Key: CLOUDSTACK-3289
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3289
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller
    Affects Versions: 4.2.0
            Reporter: Prasanna Santhanam
            Priority: Critical
             Fix For: 4.2.0


The storage code right now restricts usage of multiple image store providers in the same zone. But it restricts this even when the image store may be in a different zone/region.

>From StorageManagerImpl.java:

        // check if we have already image stores from other different providers,
        // we currently are not supporting image stores from different
        // providers co-existing
        List<ImageStoreVO> imageStores = _imageStoreDao.listImageStores();
        for (ImageStoreVO store : imageStores) {
            if (!store.getProviderName().equalsIgnoreCase(providerName)) {
                throw new InvalidParameterValueException("You can only add new image stores from the same provider " + store.getProviderName()
                        + " already added");
            }
        }

search criteria lists all add images stores:
@Override
    public List<ImageStoreVO> listImageStores() {
        SearchCriteria<ImageStoreVO> sc = createSearchCriteria();
        sc.addAnd("role", SearchCriteria.Op.EQ, DataStoreRole.Image);
        return listBy(sc);
    }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira