+++ This bug was initially created as a clone of Bug #1975534 +++ Description of problem: Production logs are spammed on "Found unpreparing host: id 08f22447-2cf1-a107-eedf-12c7421f7380 status insufficient" time="2021-06-23T20:34:11Z" level=warning msg="Found unpreparing host: id 08f22447-2cf1-a107-eedf-12c7421f7380 status insufficient" func="github.com/openshift/assisted-service/internal/cluster.(*clusterValidator).isUnPreparingHostsExist" file="/go/src/github.com/openshift/origin/internal/cluster/conditions.go:50" pkg=cluster-state time="2021-06-23T20:34:11Z" level=warning msg="Found unpreparing host: id cfcd2084-95d5-65ef-66e7-dff9f98764da status disconnected" func="github.com/openshift/assisted-service/internal/cluster.(*clusterValidator).isUnPreparingHostsExist" file="/go/src/github.com/openshift/origin/internal/cluster/conditions.go:50" pkg=cluster-state time="2021-06-23T20:34:11Z" level=warning msg="Found unpreparing host: id 5c33de86-88c5-2d9e-2d64-388855469061 status insufficient" func="github.com/openshift/assisted-service/internal/cluster.(*clusterValidator).isUnPreparingHostsExist" file="/go/src/github.com/openshift/origin/internal/cluster/conditions.go:50" pkg=cluster-state time="2021-06-23T20:34:11Z" level=warning msg="Found unpreparing host: id 2b533c42-6b90-b7c3-e25a-3db438c430c9 status disconnected" func="github.com/openshift/assisted-service/internal/cluster.(*clusterValidator).isUnPreparingHostsExist" file="/go/src/github.com/openshift/origin/internal/cluster/conditions.go:50" pkg=cluster-state time="2021-06-23T20:34:11Z" level=warning msg="Found unpreparing host: id e4243242-dd03-7eb4-fe62-1cbf9dd99644 status disconnected" func="github.com/openshift/assisted-service/internal/cluster.(*clusterValidator).isUnPreparingHostsExist" file="/go/src/github.com/openshift/origin/internal/cluster/conditions.go:50" pkg=cluster-state Version-Release number of selected component (if applicable): v1.0.22.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Why it's a warning message and do we really need it? --- Additional comment from mfilanov on 20210624T07:41:14 @lgamliel will we have the same issue with the operator? do you think it need to be backported?
@lgamliel @mfilanov Any info on how to reproduce this? Can it be verified through a normal installation flow?
@oamizur can you help Trey to reproduce it?
@mfilanov - Can you provide some steps to reproduce? I don't see this in general assisted service logs with or without a spoke cluster. (maybe that is the validation?)
The logging code was removed so it will not show up again. I'm not seeing it in any pods. Validated in DS 2.3.0-DOWNSTREAM-2021-07-12-15-34-40
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