Indeed it wasn't. I had the target pointing that way before and then I started trying to reproduce the exact behavior reported in the Bug and forgot the Snap in there.
I've now moved back but still getting 400 back instead of 500. The message below gets generated in validateRegistrant on _BaseGitNamespace by raising a GitRepositoryCreatorNotOwner as expected:
HTTP/1.1 400 Bad Request
Content-Length: 77
Content-Type: text/plain
Person-name-100279 cannot create Git repositories owned by Person-name-100277
Indeed it wasn't. I had the target pointing that way before and then I started trying to reproduce the exact behavior reported in the Bug and forgot the Snap in there.
I've now moved back but still getting 400 back instead of 500. The message below gets generated in validateRegistrant on _BaseGitNamespace by raising a GitRepositoryCr eatorNotOwner as expected:
HTTP/1.1 400 Bad Request
Content-Length: 77
Content-Type: text/plain
Person-name-100279 cannot create Git repositories owned by Person-name-100277