Bug 1975360

Summary: [4.8.0] [master] timeout on kubeAPI subsystem test: SNO full install and validate MetaData
Product: OpenShift Container Platform Reporter: Michael Filanov <mfilanov>
Component: assisted-installerAssignee: Daniel Erez <derez>
assisted-installer sub component: Deployment Operator QA Contact: bjacot
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: medium CC: aos-bugs, asegurap, derez, mfilanov, trwest
Version: 4.8Keywords: Triaged
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AI-Team-Hive KNI-EDGE-4.8
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1975359 Environment:
Last Closed: 2021-07-27 23:13:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1975359    
Bug Blocks:    

Description Michael Filanov 2021-06-23 13:51:41 UTC 
+++ This bug was initially created as a clone of Bug #1975359 +++

Description of problem:

Timeout on "SNO deploy clusterDeployment full install and validate MetaData"
subsystem test (during "Check NTP Source" step):

"
time="2021-06-22T06:42:39Z" level=info msg="API Key authentication enabled for subsystem tests" func=github.com/openshift/assisted-service/subsystem.clientcfg file="/go/src/github.com/openshift/assisted-service/subsystem/subsystem_suite_test.go:68"
[91m[1m• Failure [33.460 seconds][0m
[kube-api]cluster installation
[90m/go/src/github.com/openshift/assisted-service/subsystem/kubeapi_test.go:*40[0m
  [91m[1mSNO deploy clusterDeployment full install and validate MetaData [It][0m
  [90m/go/src/github.com/openshift/assisted-service/subsystem/kubeapi_test.go:1*31[0m

  [91mTimed out after 30.000s.
  Expected
      <bool>: false
  to be true[0m

  /go/src/github.com/openshift/assisted-service/subsystem/kubeapi_test.go:1*79
"

Additional info:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_assisted-service/2052/pull-ci-openshift-assisted-service-master-subsystem-kubeapi-aws-pools/1407221169232285696
Comment 3 Trey West 2021-07-07 16:43:42 UTC 
@derez can this be verified if recent prow tests are passing? For example, I see this test passing on this PR opened today: 

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_assisted-service/2183/pull-ci-openshift-assisted-service-master-subsystem-kubeapi-aws/1412800300070211584

Is there anything else QE can do to verify this?
Comment 5 Daniel Erez 2021-07-15 09:01:27 UTC 
(In reply to Trey West from comment #3)
> @derez can this be verified if recent prow tests are passing? For
> example, I see this test passing on this PR opened today: 
> 
> https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/
> openshift_assisted-service/2183/pull-ci-openshift-assisted-service-master-
> subsystem-kubeapi-aws/1412800300070211584
> 
> Is there anything else QE can do to verify this?

If it's passing on CI it should probably be good enough, so no need to manually verify.
Maybe just monitor the job if it fails later on.
Comment 8 errata-xmlrpc 2021-07-27 23:13:39 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