Description of problem: Using console to create HostPathProvisioner deployment fails on selecting "Create" with: Error Fix the following errors: Error "Invalid value: "string": spec.storagePools.pvcTemplate.accessModes in body must be of type array: "string"" for field "spec.storagePools.pvcTemplate.accessModes". Version-Release number of selected component (if applicable): 4.10.0 How reproducible: Always Steps to Reproduce: 1. Install OpenShift Virtualization 4.10.0 2. Instantiate OpenShift Virtualization HCO 3. Attempt to instantiate HostPathProvisioner via console Actual results: Error with following message and yaml generated: Error Fix the following errors: Error "Invalid value: "string": spec.storagePools.pvcTemplate.accessModes in body must be of type array: "string"" for field "spec.storagePools.pvcTemplate.accessModes". --- apiVersion: hostpathprovisioner.kubevirt.io/v1beta1 kind: HostPathProvisioner metadata: name: hostpath-provisioner spec: storagePools: - pvcTemplate: resources: requests: storage: 50Gi accessModes: ReadWriteOnce name: local path: /var/hpvolumes workload: nodeSelector: kubernetes.io/os: linux imagePullPolicy: IfNotPresent Expected results: Above steps should generate the following yaml per error message: apiVersion: hostpathprovisioner.kubevirt.io/v1beta1 kind: HostPathProvisioner metadata: name: hostpath-provisioner spec: storagePools: - pvcTemplate: resources: requests: storage: 50Gi accessModes: - ReadWriteOnce name: local path: /var/hpvolumes workload: nodeSelector: kubernetes.io/os: linux imagePullPolicy: IfNotPresent Additional info:
https://github.com/kubevirt/hostpath-provisioner-operator/pull/230 should be backported also to branch
... to branch release-v0.12
Waiting for the first build for v4.10.3
I am able to see the expected content in the yaml file. See attached file.
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 (OpenShift Virtualization 4.10.3 Images), 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/RHEA-2022:5675