Comment 5 for bug 1740935

Yes, I've just relaunched the machine I previously tested this with and nothing has changed. I'm not sure why there would be an expectation that anything changed, MAAS still reports version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1). I'm now running juju 2.3.4 but as previously demonstrated the juju version doesn't appear to be relevant since this is a regression between MAAS 2.2.2 and 2.3.0.

Is there a MAAS update I was suppose to check against, at least xenial packages don't appear to be any different from when this bug was opened, I feel like I'm missing something.