-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
hub OCP 4.18.0-rc.9
spoke deployment OCP 4.18.0-rc.10
ZTP site config v4.18.0-38
How reproducible:{code:none}
Always
Steps to Reproduce:
1. reference source cr in ZTP stiteconfig (StorageClass.yaml)
2. patch CR with alternate valid provisioner value
3. refresh policies app and check if rendered policy is updated
Actual results:
provisioning request value is rendered policy is always kubernetes.io/no-provisioner
using the valid value of topolvm.io doesn't reflect in the rendered policy
Expected results:
Updates to provisioner value should be present in rendered policy
Additional info:
Additional details to be added in a comment
$ oc get policies.policy.open-cluster-management.io -n helix60 ztp-group.group-du-sno-v4.18-config-policy -o yaml | grep -C6 example
objectDefinition:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
foo: bar
name: example-storage-class
provisioner: kubernetes.io/no-provisioner
reclaimPolicy: Delete
source-cr referenced: https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.18/ztp/source-crs/StorageClass.yaml
configuration in siteconfig repo:
- fileName: StorageClass.yaml
policyName: "config-policy"
metadata:
annotations:
ran.openshift.io/ztp-deploy-wave: "10"
foo: "bar"
name: example-storage-class
provisioner: topolvm.io
reclaimPolicy: Delete
- is related to
-
OCPBUGS-50656 Allow topolvm.io provisioner in reference when using LVM storage
-
- Closed
-