Description of problem (please be detailed as possible and provide log snippests): Created a custom cluster-service.yaml using placement strategies to split pods across different OCP nodes. Version of all relevant components (if applicable): $ oc version;oc get csv Client Version: 4.5.4 Server Version: 4.5.4 Kubernetes Version: v1.18.3+012b3ec NAME DISPLAY VERSION REPLACES PHASE ocs-operator.v4.5.0-552.ci OpenShift Container Storage 4.5.0-552.ci Succeeded 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)? 4 Can this issue reproducible? Yes Can this issue reproduce from the UI? No If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Install OCS operator 2. Create custom cluster-service.yaml 3. Create OCS cluster using cluster-service.yaml Actual results: OCS operator crash Expected results: OCS operator remains operational and OCS cluster deployed successfull Additional info: Added to the BZ the cluster-service.yaml used and the operator log.
@JC, you certainly hit a bug. I am still in the process of fully understanding. It is related to the way your yaml is built, and once corner case is not caught correctly. For all I can tell it is related to the fact that you don't specify a placement for the "osd" type and no placement in the DeviceSet. We need to fix the crash bug, but with a modified yaml you should be able to proceed. Can you describe what you are trying to achieve, so we can work out how to modify your yaml? Moving to 4.5.z as there should be a workaround, and such modified yamls are anyway not generated from the default GUI install.