[GitHub] [cloudstack] andrijapanicsb opened a new issue #3520: VM's ROOT disk created from ISO, honors Service offering instead of Disk offering

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

andrijapanicsb opened a new issue #3520: VM's ROOT disk created from ISO, honors Service offering instead of Disk offering
URL: https://github.com/apache/cloudstack/issues/3520
 
 
   ##### ISSUE TYPE
   
    * Bug Report
   
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   disk/service offerings
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.11.2 (didn't test previous or newer ones)
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   
   - 2 x Primary Storage pools with different Storage Tags, 
   - hypervisor (VMware tested) is irrelevant
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   NA
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   Setup:
   Service offerings are set to use (by Storage tags) storage with tag (i.e.) Primary1, while all Disk offerings are set to use another storage with tag (i.e.) Primary2
   
   Problem:
   When VM is created from a template, ROOT disk will inherit service offering setup - and will be created on Primary1 storage, as required (by storage tags). Disk offering is not used in this GUI/API call. - ALL GOOD.
   
   When VM is created from ISO, ROOT disk *should* honour the Disk offering details and choose Primary2 storage as required by storage tags - but instead, ROOT volume still honours the Service offering and gets created on Primary1 storage - WRONG.
   
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   When VM is created from ISO, ROOT disk *should* honour the Disk offering details and choose Primary2 storage as required by storage tags, intead horouring the Service offering details.
   ~~~
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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