Comment 2 for bug 1850579

Revision history for this message
Ian Booth (wallyworld) wrote :

To fix this, we need to determine if the target controller contains the source model's cloud, allowing for the fact that it might be a different name. In fact, the current checks are somewhat wrong I think. It looks like there's no check for cloud at all, expect for the side effect of adding a credential and the model with the source cloud name. This checks for a cloud with that name, but not whether it's the same cloud or not. It might just be a coincidence that the target controller has a cloud of that name.

There should I think be a check for a target controller cloud with the same fundamental connection endpoints and type, regardless of name. However, the model YAML sent across from the source controller only has cloud name and region, so there's not enough to go on.

It looks like this functionality was done 7 or so years ago, only thinking about public clouds, where just the name and region are enough to go on.