-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.12
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
TALM doesn't raise “printf variable is not supported in the template function Name field” error in the TALM log when printf variable is used in name field.
Version-Release number of selected component (if applicable):
registry-proxy.engineering.redhat.com/rh-osbs/openshift4-topology-aware-lifecycle-manager-operator-bundle-container-rhel8:v4.12.0-54
How reproducible:
100%
Steps to Reproduce:
1. Use the following template: http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/sealusa2-4.11-printfname/policygentemplates/group-du-sno-ranGen.yaml#L33
Actual results:
2022-09-30T11:53:07.222Z ERROR controllers.ClusterGroupUpgrade Policy is invalid {"error": "group-du-sno-config-policy: policy has hub template error, check the configuration policy's annotation 'policy.open-cluster-management.io/hub-templates-error' for detail"}
github.com/openshift-kni/cluster-group-upgrades-operator/controllers.(*ClusterGroupUpgradeReconciler).Reconcile
/remote-source/app/controllers/clustergroupupgrade_controller.go:189
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:298
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:253
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:214
Expected results:
“printf variable is not supported in the template function Name field”
Additional info: