Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2059659

Summary: [OCP 4.8] Backport: Fresh installation shows kube-apiserver error NodeInstallerDegraded
Product: OpenShift Container Platform Reporter: Mario Abajo <mabajodu>
Component: kube-apiserverAssignee: Abu Kashem <akashem>
Status: CLOSED WONTFIX QA Contact: Ke Wang <kewang>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: akashem, dahernan, mfojtik, wlewis, xxia
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-16 11:29:46 UTC Type: Bug
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: 1991357    
Bug Blocks:    

Description Mario Abajo 2022-03-01 16:23:51 UTC 
Description of problem:

Issue described in this bugzilla: 
  https://bugzilla.redhat.com/show_bug.cgi?id=1991357
seems to be happening in a recently installed 4.8.14 cluster:

~~~
    state:
      terminated:
        containerID: cri-o://e890534ead324e488bf9f8393b4f16baeed6cc88fdb20065e0159b966cd4bc9c
        exitCode: 1
        finishedAt: '2022-02-24T16:17:27Z'
        message: 'be-apiserver/secrets/bound-service-account-signing-key": dial tcp
          172.30.0.1:443: connect: connection refused

          I0224 16:17:26.703288       1 copy.go:24] Failed to get secret openshift-kube-apiserver/bound-service-account-signing-key:
          Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-apiserver/secrets/bound-service-account-signing-key":
          dial tcp 172.30.0.1:443: connect: connection refused

          I0224 16:17:26.964385       1 copy.go:24] Failed to get secret openshift-kube-apiserver/bound-service-account-signing-key:
          Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-apiserver/secrets/bound-service-account-signing-key":
          dial tcp 172.30.0.1:443: connect: connection refused

          W0224 16:17:27.103567       1 recorder.go:198] Error creating event &Event{ObjectMeta:{installer-11-master2.lab.ocp1.lan.16d6c51e1c445cdd  openshift-kube-apiserver    0
          0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},InvolvedObject:ObjectReference{Kind:Pod,Namespace:openshift-kube-apiserver,Name:installer-11-master2.lab.ocp1.lan,UID:838129fb-0061-4c1d-ae6c-3c63799fe4c4,APIVersion:v1,ResourceVersion:,FieldPath:,},Reason:StaticPodInstallerFailed,Message:Installing
          revision 11: Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-apiserver/secrets/bound-service-account-signing-key":
          dial tcp 172.30.0.1:443: connect: connection refused,Source:EventSource{Component:static-pod-installer,Host:,},FirstTimestamp:2022-02-24
          16:17:26.964427997 +0000 UTC m=+3.263119071,LastTimestamp:2022-02-24 16:17:26.964427997
          +0000 UTC m=+3.263119071,Count:1,Type:Warning,EventTime:0001-01-01 00:00:00
          +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:,ReportingInstance:,}:
          Post "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-apiserver/events":
          dial tcp 172.30.0.1:443: connect: connection refused

          F0224 16:17:27.103787       1 cmd.go:92] failed to copy: Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-apiserver/secrets/bound-service-account-signing-key":
          dial tcp 172.30.0.1:443: connect: connection refused

          '
        reason: Error
        startedAt: '2022-02-24T16:17:23Z'
~~~

Version-Release number of selected component (if applicable):
OCP 4.8.14
Comment 7 Michal Fojtik 2023-01-16 11:29:46 UTC 
Dear reporter, we greatly appreciate the bug you have reported here. Unfortunately, due to migration to a new issue-tracking system (https://issues.redhat.com/), we cannot continue triaging bugs reported in Bugzilla. Since this bug has been stale for multiple days, we, therefore, decided to close this bug.

If you think this is a mistake or this bug has a higher priority or severity as set today, please feel free to reopen this bug and tell us why. We are going to move every re-opened bug to https://issues.redhat.com. 

Thank you for your patience and understanding.
Comment 8 Red Hat Bugzilla 2023-09-18 04:32:47 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days