Success Message When Creating ACL but No ACL Items Found

[kiranya-eevuri]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

I encountered an issue while trying to create an ACL using the Kafka UI. After submitting the ACL creation form, I receive a success message indicating that the ACL has been created successfully. However, when I check the ACL list, it shows "No ACL items found."

I have refreshed the page and cleared the cache but the issue persists.

Expected behavior

The newly created ACL should appear in the list of ACLs. It's similar to creating a group and assigning specific access rights to that group; the users within that group must have the corresponding access. This functionality is essential for effective access management.

Your installation details

Application I have deployed in Openshift Redhat

1. App version - 2956664
2. helm chart - v3.9.3

Steps to reproduce

1. Log in to Kafka UI:
   Navigate to the Kafka UI login page.
   Enter your credentials and log in.

2. Access the ACL Management:
   From the main dashboard, select the "ACLs" option in the navigation menu.

3. Create a New ACL:
   Click on the "Create ACL" button.
   Fill in the required fields:
   ACL Type: Select "Custom ACL".
   Principal: Enter a valid principal (e.g., User:your_username).
   Host Restriction: Enter the host.
   Resource Type: Choose "TOPIC".
   Operations: Select the desired operations (e.g., ALLOW, DENY, etc.).
   Click "Submit" to create the ACL.

4. Check ACL List:
   After the success message appears, refresh the ACL list.
   Note that the list still shows "No ACL items found".

Screenshots

Logs

I checked the logs, and it shows that the ACL was created:
DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: kafka-dev
2024-10-09 13:20:28,269 DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Start getting metrics for kafkaCluster: kafka-dev
2024-10-09 13:20:28,678 DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: kafka-dev
2024-10-09 13:20:55,666 INFO [reactor-http-epoll-4] i.k.u.s.a.AclsService: CREATING ACL: [user:kiranya.eevuri,TOPIC,PREFIXED,A,READ,ALLOW,]
2024-10-09 13:20:55,670 INFO [parallel-1] i.k.u.s.a.AclsService: ACL CREATED: [user:kiranya.eevuri,TOPIC,PREFIXED,A,READ,ALLOW,]
2024-10-09 13:20:58,269 DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Start getting metrics for kafkaCluster: kafka-dev
2024-10-09 13:20:58,523 DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: kafka-dev
2024-10-09 13:21:28,269 DEBUG [parallel-1] i.k.u.s.ClustersStatisticsScheduler: Start getting metrics for kafkaCluster: kafka-dev

Additional context

If I use this env " - name: SPRING_CONFIG_ADDITIONALLOCATION
value: /roles.yml "

And deploy in openshift, showing "No clusters Found"
No info was there in UI page.

But when I remove that env and deploy, I am able see info and options..etc

[github-actions]

Hi kiranya-eevuri! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[Haarolean]

Having 'Acl created' log message means we've done our part (the call via kafka client has succeeded).

• What kind of kafka and which version are you running?
• Have you tried reproducing this in other clusters?

We'd need a minimal reproducible example for this, as this works in our environments. Feel free to use this as a reference.

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[kiranya-eevuri]

1. Kafka version: 3.5.2

2. We are currently testing Kafka UI in our test environment only. The Kafka instance is hosted on Cloudera, and we are using Kerberos authentication to connect to the Kafka cluster