Description of problem (please be detailed as possible and provide log snippests): After deletion of onboarding-ticket-key the onboarding ticket generation job did not re-trigger for non onboarded clusters. Version of all relevant components (if applicable): ODF version: 4.14.4-4.fusion-hci OCP version: 4.14.5 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, as unable to delete the onboarding-ticket-generation job. 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: no Steps to Reproduce: 1. Create one provider-client hci cluster with odf 4.14.4-4. 2. Check ux-backend-server pod is up and running 3. Check below secrets are available under secrets for 'openshift-storage' namespace onboarding-private-key onboarding-secret-generator-dockercfg onboarding-secret-generator-token and onboarding-ticket-key 4. Check onboarding-secret-generator job is in 'Completed' status. 5. Delete onboarding-ticket-key Actual results: After deletion of onboarding-ticket-key the onboarding ticket generation job did not re-trigger. Expected results: After deletion of onboarding-ticket-key the onboarding ticket generation job should be re-triggered. Additional info:
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.15.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:1383