web-ui: Project creation - project creation is stuck in UI with timeout error.

[ss5829]

Nokia build of Intel EMF v2026

Using a project manager user a project(test02) is created, it was observed that the project creation is going to Timeout errored state after sometime.
However in Keycloak the 5 default groups for the corresponding project are created successfully.

There are no noticeable errors in the app-orch-tenant-controller pod logs too,

{"level":"INFO","time":"2026-04-09T09:14:19.136Z","caller":"southbound/app-deployment.go:83","message":"display name list size : 0"}
{"level":"INFO","time":"2026-04-09T09:14:19.140Z","caller":"plugins/plugin.go:71","message":"Successfully processed event {create nokia test02 3d317bfc-a0ee-4b80-83e5-8a5df213ab4f 0xc0014031f0} by Extensions Provisioner"}
{"level":"INFO","time":"2026-04-09T09:14:19.142Z","caller":"plugins/plugin.go:77","message":"Done dispatching event: {create nokia test02 3d317bfc-a0ee-4b80-83e5-8a5df213ab4f 0xc0014031f0}"}
{"level":"INFO","time":"2026-04-09T09:14:19.142Z","caller":"nexus/nexus-hook.go:186","message":"Setting watcher manifest tag for project test02 to v1.5.11"}
{"level":"INFO","time":"2026-04-09T09:14:19.164Z","caller":"manager/manager.go:126","message":"Done with create on worker 0 for project test02 elapsed time 144 seconds"}

This issue was previously seen in Nokia build of v2025.02 instance as well. A re-deployment was done to solve that issue.

In order to understand the issue better can you please provide us with the sequence of flow during the project creation,
like the set of instructions sent from UI,
the list & order of the pods involved,
the database / tables that are modified.

also could this be a mere UI issue where the web-ui is unable to get the desired state change from keycloak hence it displays a timeout error.

please comment.

CC: @scottmbaker , @guptagunjan , @amathan, @Amithpn

more info in ticket: #654

[scottmbaker]

@ss5829 my first reaction is that I don't think this is a UI issue, but is a problem in the backend. It's interesting that it's affecting all of the tenant controllers for the project instead of just one. Previous bug reports were often about a single tenant controller or a pair of them lagging behind the rest. Could you take a look inside the logs of the tenancy-manager pod and see if there's anything telling in there? Also check it's status to make sure it is healthy and running.

It may also be helpful to look at the projectactivewatchers. First, make sure they have been created for the org and project. There should be one for each tenant controller. Then take a look and see what the statusIndicator is set to.

Finally, you can also look at the projects.project.edge-orchestrator.intel.com for the project. This would help us isolate whether it was a backend or a UI issue. It should have the statusIndication for the project.