Open msschl opened 2 months ago
@Zerpet Have you ever seen anything like this?
Without server logs, my best guess is a permission issue. Your user admin
can login, but it may not have any permissions to list/read other resources.
@Zerpet The user has the tag administrator set. So in theory it should be able to see everything
λ kubectl -n rabbitmq exec rabbitmq-ha-server-0 -it -- rabbitmqctl list_permissions -p /dev
Defaulted container "rabbitmq" out of: rabbitmq, default-user-credential-updater, vault-agent, vault-agent-init (init), setup-container (init)
Listing permissions for vhost "/dev" ...
user configure write read
admin .* .* .*
λ kubectl -n rabbitmq exec rabbitmq-ha-server-0 -it -- rabbitmqctl list_permissions -p /
Defaulted container "rabbitmq" out of: rabbitmq, default-user-credential-updater, vault-agent, vault-agent-init (init), setup-container (init)
Listing permissions for vhost "/" ...
user configure write read
admin .* .* .*
λ kubectl -n rabbitmq exec rabbitmq-ha-server-0 -it -- rabbitmqctl list_user_permissions admin
Defaulted container "rabbitmq" out of: rabbitmq, default-user-credential-updater, vault-agent, vault-agent-init (init), setup-container (init)
Listing permissions for user "admin" ...
vhost configure write read
/ .* .* .*
/dev .* .* .*
How can I see the logs?
@Zerpet what do you need to further asses this issue? The user has the right permission. Created resources through the UI can be viewed and modified. Resources created by the operator can not be viewed by the UI…
Describe the bug
Resources created by the messaging-topology-operator exists and can be used by producers and consumers. When trying to access the resource in the management UI it returns "not found" for the resource
To Reproduce
Steps to reproduce the behavior:
Expected behavior Created resources by the messaging-topology-operator are shown in the management UI
Screenshots
As you can see the virtual hosts are created by the messaging-topology-operator
Clicking on the resource results in:
Version and environment information
Additional context
Using all created resources from code, i.e., our running services, also works: