Are you saying there was no primary storage tagged "bar"? If that is the case, I guess I would expect the deployment of the VM to fail because not all of the criteria could be met.
On Thu, Jan 9, 2014 at 7:08 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > Is this a bug (perhaps fixed), or expected behavior? > > If I create a service offering with storage tag=foo, and a disk > offering with storage tag=bar, I cannot provide this disk offering as > a data disk to deploy along with this service offering. The root > volume gets allocated, and then the data disk fails. > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
