So, in trying to work on a fix, I'm really struggling to reproduce the original error in test code. The only way I can get it to fail is if 'username' of '*_username' is in the relation data.
@Christopher; please could you provide the output of `juju show-unit rabbitmq-server/0` and
I'd like to check whether `username` is actually in the databag on the rabbitmq-server unit:
If you run: `juju exec -u rabbitmq-server/0 -- relation-ids amqp` it'll respond with something like `amqp:2`.
Then if you run `juju exec -u rabbitmq-server/0 -- relation-get -r amqp:2 - flask-rabbitmq/0`
It should show a databag that looks something like:
So, in trying to work on a fix, I'm really struggling to reproduce the original error in test code. The only way I can get it to fail is if 'username' of '*_username' is in the relation data.
@Christopher; please could you provide the output of `juju show-unit rabbitmq-server/0` and
I'd like to check whether `username` is actually in the databag on the rabbitmq-server unit:
If you run: `juju exec -u rabbitmq-server/0 -- relation-ids amqp` it'll respond with something like `amqp:2`.
Then if you run `juju exec -u rabbitmq-server/0 -- relation-get -r amqp:2 - flask-rabbitmq/0`
It should show a databag that looks something like:
egress-subnets: 172.20.0.183/32
ingress-address: 172.20.0.183
private-address: 172.20.0.183
username: flask-rabbitmq/0
vhost: openstack
I'm seeking to verify that the username key is present.
Thanks.