Comment 10 for bug 1735402

Okay, we need to really get this sorted out, we've got an haproxy unit we can't manage (it changed IPs) in jaas-west-europe and we can't add a new one there. Here's what I did in jaas-azure-west-europe which is demonstrating this issue:

1. juju update-credentials azure jaas-prodstack-cdo-azure, went through the portal login and OAuth process, add-unit still fails, this is all using the correct Azure subscription ID, I can see all the JaaS resources under this subscription.
2. juju add-credentials azure jaas-test-credentials, went through the portal login and OAuth process
3. juju set-default-credentials azure jaas-test-credentials, add-unit still fails
4. Locally, juju add-credentials azure jaas-test-credentials, went through the processs, juju bootstrap works.

To my mind that "proves" the credentials work, at least in a clean environment. Is it possible the controller is stuck using an old URL to do the VM sizes query, which is what's (apparently) failing? Are there controller logs or information on the controller that I can compare against my locally generated secrets to make sure it's using the same set?