Description of problem: When using a nodeSelector in the spec section of the SpecialResource, if there are no matching nodes SRO enters a crash loop. Version-Release number of selected component (if applicable): How reproducible: Use non-matching labels in the nodeSelector section of SpecialResource.spec Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified on 4.10.9. No error message is logged anywhere but if you look at the daemonset you can easily see that the selector is wrong and figure out from there that the driver won't get built. When fixing the templates and updating the configmap things run again.
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: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069