[
https://issues.apache.org/jira/browse/CLOUDSTACK-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391549#comment-15391549
]
Christian Meier commented on CLOUDSTACK-9433:
---------------------------------------------
Regarding: "Its far easier to migrate to service offering that has a tag VS
updating an existing service offering with a tag."
Yes, exactly 100% my opinion, I just want the api to exactly do the easier
method and allow me to migrate a VM to a service offering that has a storage
tag while the currently associated offering of the VM has no storage tag
attached. It is just not allowed and throws the aforementioned error, that new
service offering should have tags as subset of current service offering tags.
If the current offering has no tags and you want to switch to one with a
storage tag, it simply stopped by this error which means only removing storage
tags is possible.
> Change of VM compute offering with additional storage tags not allowed
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-9433
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9433
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.8.0
> Reporter: Christian Meier
>
> It is not possible to upgrade service offerings of a with no storage tags to
> a offering with a storage tag.
> The UI does not show a newly created Service Offering which has defined a
> Storage Tag. If tried through cloudmonkey, the error reports :
> "Unable to upgrade virtual machine; the new service offering should have tags
> as subset of current service offering tags. Current service offering tags:
> []; new service offering tags: [RootLun]"
> While I understood the error message in the first place, it seems to me an
> artificially introduced restriction which does not reflect real circumstances.
> Usually users start without using a sophisticated tagging scheme. Later on
> while already having instantiated VMs, and maybe getting additional primary
> storage they want to refine their usage scheme. They start to create
> offerings with storage tags. All existing machines cannot migrate to these
> new service offerings but must be completely reinstalled.
> (An automatic storage migration might be an additional option, but I think
> still the ROOT admin can manually migrate the existing volumes if necessary.)
> More importantly, I think the artificial restriction must be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
