Bug 1969773 - [4.8.0] Empty cluster name on handleEnsureISOErrors log after applying InfraEnv.yaml
Summary: [4.8.0] Empty cluster name on handleEnsureISOErrors log after applying InfraE...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.0
Assignee: Elior Erez
QA Contact: bjacot
URL:
Whiteboard: KNI-EDGE-JUKE-4.8 AI-Team-Hive
Depends On: 1969766
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-09 08:57 UTC by Michael Filanov
Modified: 2021-07-27 23:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1969766
Environment:
Last Closed: 2021-07-27 23:12:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift assisted-service pull 2065 0 None open [ocm-2.3] Bug 1969773: Fix empty cluster name after applying InfraEnv.yaml 2021-06-27 07:37:29 UTC
Red Hat Bugzilla 1969766 1 low CLOSED [master] Empty cluster name on handleEnsureISOErrors log after applying InfraEnv.yaml 2021-10-18 17:33:39 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:12:41 UTC

Description Michael Filanov 2021-06-09 08:57:12 UTC
+++ This bug was initially created as a clone of Bug #1969766 +++

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:

Comment 5 nshidlin 2021-07-05 11:54:56 UTC
Verified with: 2.3.0-DOWNSTREAM-2021-07-02-22-02-33

time="2021-07-05T11:52:35Z" level=info msg="Image sno-0 being prepared for cluster sno-0" func="github.com/openshift/assisted-service/internal/controller/controllers.(*InfraEnvReconciler).handleEnsureISOErrors" file="/remote-source/assisted-service/app/internal/controller/controllers/infraenv_controller.go:360" go-id=828 infra_env=sno-0 infra_env_namespace=sno-0 request_id=f98c5010-bb7e-421f-b4c0-8497153cc5e1

Comment 7 errata-xmlrpc 2021-07-27 23:12:22 UTC
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.8.2 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:2438


Note You need to log in before you can comment on or make changes to this bug.