openstack-integrator charm blocked with invalid value for credentials config

Hi all,

It seems that my bug may be a duplicate of (1867097) but I will explain my issue anyway as that bug does not go into detail about what was attempted to resolve the issue.

Overview:

I am deploying Charmed Kubernetes on a third-party Openstack, specifically the T-Systems OTC Cloud.
I have managed to bootstrap and deploy the solution but I am hitting issues with the Openstack Integrator charm where it is stuck in a "invalid value for credentials config" blocked state.Deploying load-balancers or storage using Cinder CSI driver does not work.

My bundle is fairly standard, I have used Kubernetes-Core with the integrator deployed on either node 0 or 1.

Fixes Attempted:

* First I tried the standard method of co-locating integrator charm on host 0/1 with Juju provided credentials configured via juju trust. This did not work, despite the fact I used the credentials to deploy the cluster.

* I then tried to configure the credentials by base64 encoding the config as json and using the credentials parameter, but that gives me the same invalid error. I.E this json fed into base64 tool and then passed to Juju via juju config command:

{
  "auth-url"":'https://iam.eu-de.otc.t-systems.com/v3',
  "username": 'doggo',
  "password": 'woof',
  "tenant-id": doggo-internal-network-id,
  "domain-id": doggo-external-network-id
}

* After this failed, I then tried to manually specify the username, password, and domain/tenant ID(s) as charm options in the bundle. This also did not work and gave the same error.

* I also tried to put the the integrator charm onto LXD on node 0/1 to see if this made any difference, but did nothing.

* Finally I tried to create the cloud conf manually and got further, it deployed the csi plugin but storage and load-balancers were still blocked. I might have to retry this route if all else fails.

I couldn't find anything meaningful in the juju logs or in any of the other logs to lead me to why the credentials are invalid.

Happy to provide direct access to the Openstack or any extra information as required.

Cheers,

- Calvin