install failed: deployment vdo-controller-manager not ready before timeout

[erezbatish]

Hi There I deployed VDO 0.2.0 on OpenShift version 4.9.25, after VDO deployment I'm getting an error: install failed: deployment vdo-controller-manager not ready before timeout: deployment "vdo-controller-manager" exceeded its progress deadline

Looking at the vdo-controller-manager deployment status I see the following: _status: observedGeneration: 3 unavailableReplicas: 1 conditions:

• type: Available status: 'True' lastUpdateTime: '2022-04-03T13:19:45Z' lastTransitionTime: '2022-04-03T13:19:45Z' reason: MinimumReplicasAvailable message: Deployment has minimum availability.
• type: ReplicaFailure status: 'True' lastUpdateTime: '2022-04-03T13:19:45Z' lastTransitionTime: '2022-04-03T13:19:45Z' reason: FailedCreate message: >- pods "vdo-controller-manager-6746fcc96d-" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider restricted: .spec.securityContext.hostNetwork: Invalid value: true: Host network is not allowed to be used, spec.volumes[0]: Invalid value: "hostPath": hostPath volumes are not allowed to be used, spec.containers[0].securityContext.hostNetwork: Invalid value: true: Host network is not allowed to be used, spec.containers[0].securityContext.containers[0].hostPort: Invalid value: 8443: Host ports are not allowed to be used, spec.containers[1].securityContext.hostNetwork: Invalid value: true: Host network is not allowed to be used, spec.containers[1].securityContext.containers[0].hostPort: Invalid value: 8443: Host ports are not allowed to be used, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "machine-api-termination-handler": Forbidden: not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable by user or serviceaccount, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "vdo-scc": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]
• type: Progressing status: 'False' lastUpdateTime: '2022-04-03T13:29:46Z' lastTransitionTime: '2022-04-03T13:29:46Z' reason: ProgressDeadlineExceeded message: >- ReplicaSet "vdo-controller-manager-6746fcc96d" has timed out progressing._

I created the required SCC prior to the VDO deployment per the Getting Started Guide, this is how the SCC YAML looks like after creation:

_allowHostPorts: true priority: null requiredDropCapabilities: null allowPrivilegedContainer: true runAsUser: type: RunAsAny users:

• - system:serviceaccount:vsphere-kubernetes-drivers-operator:vdo-controller-manager

• 'system:serviceaccount:vmware-system-csi:vsphere-csi-node' allowHostDirVolumePlugin: true allowHostIPC: false seLinuxContext: type: RunAsAny readOnlyRootFilesystem: false metadata: creationTimestamp: '2022-04-03T13:40:01Z' generation: 1 managedFields:
  • apiVersion: security.openshift.io/v1 fieldsType: FieldsV1 fieldsV1: 'f:seLinuxContext': .: {} 'f:type': {} 'f:defaultAddCapabilities': {} 'f:allowHostNetwork': {} 'f:users': {} 'f:runAsUser': .: {} 'f:type': {} 'f:allowHostPorts': {} 'f:allowPrivilegedContainer': {} 'f:allowHostDirVolumePlugin': {} 'f:fsGroup': .: {} 'f:type': {} manager: Mozilla operation: Update time: '2022-04-03T13:40:01Z' name: vdo resourceVersion: '137231' uid: 8fda80bc-ad5e-4dc7-ae49-ca49b9ad7634 fsGroup: type: RunAsAny groups: [] kind: SecurityContextConstraints defaultAddCapabilities:
• SYS_ADMIN supplementalGroups: type: RunAsAny volumes:
• '*' allowHostPID: false allowHostNetwork: true allowPrivilegeEscalation: true apiVersion: security.openshift.io/v1 allowedCapabilities: null_

Can you please advise? The SCC looks OK and per instructions. Thanks

[erezbatish]

Issue resolved, the name of the namespaces was incorrect, the name space name was "vsphere-kubernetes-driver-operator" while in the SCC it was "vsphere-kubernetes-drivers-operator".