chrxmvtik commented on issue #148: URL: https://github.com/apache/cloudstack-terraform-provider/issues/148#issuecomment-2537107279
> @chrxmvtik I just tested with an `unconstrained` offering and get the same error as you when trying to update an existing instance that had a different offering and was going to change it, but if you create the instance from scratch and specify the `details`, it will work! > > I got the same error as you only when I initially tried to change the offering from `constrained` to `unconstrained`. If the instance is already using the `unconstrained` and I try to change the CPU (for example), then it will behave the same as `constrained` and show no issue it TF apply, but not actually change anything. > > I still think this is an upstream [issue](https://github.com/apache/cloudstack/issues/6865) with apache/cloudstack that needs to be resolved. Ah yes, thanks! When I created a new instance with g1.Custom service offering then everything worked fine and I was able to define resources using details parameter. Seems like an workaround for a while.. -- 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. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
