Description of problem: After applying InfraEnv.yaml the cluster name is empty on the log message: `time="2021-06-08T16:50:21Z" level=info msg="Image myinfraenv being prepared for cluster " func="github.com/openshift/assisted-service/internal/controller/controllers.(*InfraEnvReconciler).handleEnsureISOErrors" file="/go/src/github.com/openshift/origin/internal/controller/controllers/infraenv_controller.go:344" go-id=562 infra_env=myinfraenv infra_env_namespace=default request_id=9b15c534-b835-474d-9514-53faf2a5c6f5 ` https://github.com/openshift/assisted-service/blob/81a252cd6ee42175410e7da038a5ac4d237aa71a/internal/controller/controllers/infraenv_controller.go#L344 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy the service skipper make deploy-test 2. Enable KubeApi - skipper make enable-kube-api-for-subsystem 3. Apply yamls on docs/crds - https://github.com/openshift/assisted-service/tree/master/docs/crds by the following order: - clusterDeployment.yaml - agentClusterInstall.yaml - pullsecret.yaml - clusterImageSet.yaml - infraEnv.yaml Actual results: Log message: "Image myinfraenv being prepared for cluster " Expected results: "Image myinfraenv being prepared for cluster <cluster_name>" Additional info:
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759