[ https://issues.apache.org/jira/browse/CLOUDSTACK-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030011#comment-14030011 ]
ASF subversion and git services commented on CLOUDSTACK-6907: ------------------------------------------------------------- Commit 43e479d238649e3ab61259b6b57e56152f1ecb29 in cloudstack's branch refs/heads/4.4-forward from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=43e479d ] CLOUDSTACK-6907: lisVolumes - make a decision whether to set service or disk offering in the response, based on the DiskOfferingVO type entry, not the volume Type > listVolumes: diskOfferingId is returned for the volume instead of service > offering id, if its a root volume detached from the vm > -------------------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-6907 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6907 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.4.0 > Reporter: Alena Prokharchyk > Assignee: Alena Prokharchyk > Fix For: 4.5.0 > > > Steps to reproduce: > 1) Deploy vm. Stop it. > 2) Detach the Root volume. It becomes a DataDisk > 3) execute listVolumes call. > Bug: volumes that were originally created as Root, reference service offering > instead of a disk offering. But the API just assumes that if the disk Type is > DataDisk, then diskOffering should be returned. > Api has to be smarter while figuring out what to return - service or disk > offering id - and return the service offering if thats what the id of the > offering represents. -- This message was sent by Atlassian JIRA (v6.2#6252)