Travis Nielsen

@epuertat The `set-rgw-credentials` fails in the rook toolbox. Perhaps the way rook names the realm, zone, and zonegroup isn't compatible? Would you expect the old way to be broken though?...

> @travisn that last error message [point to this code](https://github.com/ceph/ceph/blob/75c4960abf3b81ff7c6f36e816e1c6a29ceabc9e/src/pybind/mgr/dashboard/services/rgw_client.py#L267). As you may see it's mostly consuming the radosgw-admin from the CLI. That failure might mean that the CLI tool...

> expected user is `dashboard` So the `ceph dashboard set-rgw-credentials` should be creating the `dashboard` user when it isn't found, right?

@galexrt Looks like #10137 is related to this, but you must not have seen this repro either in your testing. We can close this issue, right?

It seems I'm the only one not seeing the object store not working. Are you testing in minikube as well? Even testing with #10137 I still see that the dashboard...

Yes, it has a dashboard key configured in the test cluster: ``` $ ceph dashboard get-rgw-api-access-key M361YN2M3A2ONW24AO2Z $ ceph dashboard get-rgw-api-secret-key CdnwRhCLbiuGbKY6mpj1BTeKjGlo9IZ1EncOiBAQ ``` I tried both with v16 and v17,...

> @travisn Are you getting the same error in the logs? I'll try to reproduce it tomorrow. The error in the logs is still the same as posted [earlier](https://github.com/rook/rook/issues/9660#issuecomment-1026323910). Do...

> Does this still happen with the latest v1.9.2 release? With the latest master I still see the same failure. Was there a related change you hoped would fix it?

You're creating the example object-external.yaml? @parth-gr could you take a look? Looks like there was a fix in #9633, but seems another fix is needed.

@jclab-joseph I was referring to [this example external object manifest](https://github.com/rook/rook/blob/master/deploy/examples/object-external.yaml).