[GitHub] borisstoyanov opened a new issue #2758: storage_pool_details overprovisiohnning settings are being picked up as a tag

[GitBox <gi...@apache.org>]

borisstoyanov opened a new issue #2758: storage_pool_details overprovisiohnning settings are being picked up as a tag
URL: https://github.com/apache/cloudstack/issues/2758
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Storage
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.12
   ~~~
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   When user uses the updateConfiguration api: 
   ~~~
   update configuration name = "storage.overprovisioning.factor" value = 2.0 storageid = [pool.id]
   ~~~
   Cloudstack api creates a record in the storage_pool_details table looking like that: 
   ~~~
   MariaDB [cloud]>  select * from storage_pool_details;
   +----+---------+---------------------------------+-------+---------+
   | id | pool_id | name                            | value | display |
   +----+---------+---------------------------------+-------+---------+
   |  2 |       2 | storage.overprovisioning.factor | 2.0   |       1 |
   +----+---------+---------------------------------+-------+---------+
   1 row in set (0.00 sec)
   ~~~
   At this point if you try to migrate a volume and change it's disk offering, it fails with 
   
   ~~~
   {errorcode : 431, errortext : u'Target Storage [id=26055c44-abb2-3ec6-8098-3c7f067e6d34] tags [storage.overprovisioning.factor] does not match new disk offering [id=637a5ded-3fba-4eda-9515-fc5218d1c905] tags [null].'}
   ~~~ 
   
   Which makes me think that cloudstack thinks this setting is actually a tag and fails the operation.
   
   There are no other setting or tags at the storage at this moment that might cause this. 
   
   ~~~
   MariaDB [cloud]>  select * from storage_pool_details;
   +----+---------+---------------------------------+-------+---------+
   | id | pool_id | name                            | value | display |
   +----+---------+---------------------------------+-------+---------+
   |  2 |       2 | storage.overprovisioning.factor | 2.0   |       1 |
   +----+---------+---------------------------------+-------+---------+
   1 row in set (0.00 sec)
   
   MariaDB [cloud]>  select * from storage_pool_tags;
   Empty set (0.00 sec)
   
   ~~~
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   - Deploy a VM and attach a small disk to it
   - with cloudmonkey execute: update configuration name = "storage.overprovisioning.factor" value = 2.0 storageid = [target.pool.id]
   - with cloudmonkey execute: migrate volume volumeid=[vol.id] storageid=[target.pool.id] newdiskofferingid=[large.disk.off.id]
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   I would expect that the volume is migrated with new disk offering
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   It fails with:
   {errorcode : 431, errortext : u'Target Storage [id=26055c44-abb2-3ec6-8098-3c7f067e6d34] tags [storage.overprovisioning.factor] does not match new disk offering [id=637a5ded-3fba-4eda-9515-fc5218d1c905] tags [null].'}
   
   which looks like the overriding overprovisiohnning setting is taken as a tag. Note that there are no tags to the pool or offering at this time that might interfere.
   ~~~
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services