Description of problem (please be detailed as possible and provide log snippets): when noobaa migration job fails (after all retries failed according to backoff limit), the job pod is deleted and there are no logs available to investigate the failure Version of all relevant components (if applicable): OCS 4.7 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)? 3 Can this issue reproducible? only by using a noobaa-core image that was changed to always fail migration Can this issue reproduce from the UI? no If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: * the migration job pod is deleted after failure Expected results: * when the job fails the pod should be left for investigation Additional info:
changed the restartPolicy in the migration job to "Never". this will keep failed pods and not delete them
The migration pod is kept in case of a failure in the migrate job. Verified with v4.7.0-318.ci See https://bugzilla.redhat.com/show_bug.cgi?id=1938557#c8
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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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-2021:2041