Description of problem (please be detailed as possible and provide log snippests): When ux pod is unavailable if we try to trigger onboarding token then it does not generate but its just stuck at generating. A proper error message should be displayed. Version of all relevant components (if applicable): OCP version: 4.14.11 ODF version: 4.14.5-8 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: NA Steps to Reproduce: 1. Log in to UI, check ux pod is up and running 2. For openshift-storage namespace, Workloads-->Deployments-->ux-backend-server deployment Scale down the pod count to 0 3. Check no ux pod is up and running. 4. From Storage-->Storage Clients click on 'Generate client onboarding token' 5. It keep on generating state and no token generated but no error message displayed. Actual results: When ux pod is unavailable if we try to trigger onboarding token then it does not generate but its just stuck at generating no error message displayed. Expected results: When ux pod is unavailable if we try to trigger onboarding token then it does not generate but its just stuck at generating. A proper error message should be displayed. Additional info:
Moving out of 4.15 a sits minor issue
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:4591