Marcus Sorensen created CLOUDSTACK-1791:
-------------------------------------------

             Summary: Volumes with storage tags can't be attached
                 Key: CLOUDSTACK-1791
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1791
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller
    Affects Versions: 4.1.0
            Reporter: Marcus Sorensen
            Priority: Blocker
             Fix For: 4.1.0


I'm reporting this because it was on the mailing list and is still an issue. 
The customer-facing symptom is that volumes created with storage tags can't be 
attached to virtual machines.


A new column was added to storage_pool, called storage_provider_id.  When 
trying to access a StoragePoolVO instance (when I go to attach a volume to a 
VM) I popped a null pointer.  This may be related to CLOUDSTACK-1547, but I'm 
not sure yet.
The bigger issue in my mind though, is the fact that the assert in 
GenericDaoBase wasn't tripped! (line 1683)
assert (attr != null) : "How come I can't find " + meta.getCatalogName(index) + 
"." + meta.getColumnName(index);

My questions are.

Why doesn't the default startup for cloudstack "mvn -pl :cloud-client-ui 
jetty:run" enable asserts? (the -ea flag)?
Why in the world is SqlGenerator using STAR in it's queries?  I've pasted the 
query it generated below.  This new column isn't mapped as an attribute.
SELECT storage_pool.* from storage_pool LEFT JOIN storage_pool_details ON 
storage_pool.id = storage_pool_details.pool_id WHERE storage_pool.removed is 
null and storage_pool.data_center_id = 1 and (storage_pool.pod_id = 1 or 
storage_pool.pod_id is null) and (storage_pool.cluster_id = 1 OR 
storage_pool.cluster_id IS NULL) AND (((storage_pool_details.name='bssan') AND 
(storage_pool_details.value='true'))) GROUP BY storage_pool_details.pool_id 
HAVING COUNT(storage_pool_details.name) >= 1

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

Reply via email to