MAAS Space Case Sensitivity Error

Hello,

I currently ran into an interesting issue using Juju 2.7.0 and MAAS as the cloud. I needed to kill a controller and recreate it due to my own user error. However, when I went to recreate it via bootstrap, it could not find the Space. I tried to manually add it to Juju however since the controller was not yet created I couldn’t. Below was the error (ip masked):

2019-12-13 21:50:05 DEBUG juju.network network.go:517 addresses after filtering: [local-cloud:X.X.X.X@UF(id:3)]
2019-12-13 21:50:05 DEBUG juju.state spacesdiscovery.go:170 Adding space mgmt from provider 2
2019-12-13 21:50:05 DEBUG juju.state spacesdiscovery.go:170 Adding space uf from provider 3
2019-12-13 21:50:05 DEBUG juju.state spacesdiscovery.go:170 Adding space docker from provider 1
2019-12-13 21:50:05 DEBUG juju.state open.go:180 closed state without error
ERROR space with name “UF” not found
2019-12-13 21:50:05 DEBUG cmd supercommand.go:519 error stack:
/workspace/_build/src/github.com/juju/juju/core/network/address.go:391: space with name “UF” not found

I then tested to see if case sensitivity was the issue so I went into MAAS and changed “UF” to “uf” due to the “Adding space uf from provider 3” log entry. When I did this, it worked. My question is why is case sensitivity a problem now when it wasn’t before or why isn’t it just using “UF”?

1 Like

Hi @arod412, welcome to the community.

I’ve created a bug on Launchpad to track this:
https://bugs.launchpad.net/juju/+bug/1856537

1 Like

We hope to release 2.7.2 next week, which will have a fix for this.