In the scenarios described, can you please include the actual juju commands run to add the machines? The bug says "Effect: It doesn't work" but it's hard to diagnose without knowing how the machines were added or app deployed. ie I am not sure why the default-space setting isn't working without knowing the exact juju commands used to deploy an app or add a machine.
It would be interesting to do another experiment. add-machine and deploy take a constraints argument. If not specified, it falls back to the model constraint.
So, this
juju add-machine --constraints "spaces=gamma"
or this
juju deploy foo --constraints "spaces=gamma"
would have the same effect as adding a model constraint "spaces=gamma" and omitting the constraint with the deploy. I wonder if using the above works for you.
Anyway, if you could provide more info that would be great. I'll mark as Incomplete for now.
In the scenarios described, can you please include the actual juju commands run to add the machines? The bug says "Effect: It doesn't work" but it's hard to diagnose without knowing how the machines were added or app deployed. ie I am not sure why the default-space setting isn't working without knowing the exact juju commands used to deploy an app or add a machine.
It would be interesting to do another experiment. add-machine and deploy take a constraints argument. If not specified, it falls back to the model constraint.
So, this
juju add-machine --constraints "spaces=gamma"
or this
juju deploy foo --constraints "spaces=gamma"
would have the same effect as adding a model constraint "spaces=gamma" and omitting the constraint with the deploy. I wonder if using the above works for you.
Anyway, if you could provide more info that would be great. I'll mark as Incomplete for now.