After successfully installing the cluster on AWS IPI, some installer pods are encountering an error state due to the following issue:  NAMESPACE                                         

 NAME                                                                        READY   STATUS      RESTARTS        AGE
openshift-etcd                                     installer-7-ip-10-0-12-94.ap-south-1.compute.internal                       0/1     Error       0               5h10m
openshift-kube-scheduler                           installer-5-ip-10-0-12-94.ap-south-1.compute.internal                       0/1     Error       0               5h7m

ETCD installer logs
===================

F0224 06:45:58.537203       1 cmd.go:109] Get "https://172.30.0.1:443/api/v1/namespaces/openshift-etcd/pods?labelSelector=app%3Dinstaller": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

kube-scheduler installer logs
=============================

F0224 06:49:17.038193       1 cmd.go:109] Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-scheduler/pods?labelSelector=app%3Dinstaller": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

    4.18.1

So far, I have deployed the cluster twice and encountered this issue both times. I also checked with my colleagues' clusters and found the same issue.

1. Install the cluster on AWS using the IPI method.
2. After the installation is complete, some installer pods appear in an error state.

Installer pods are in error state.

    Every pod should be in either a Running or Completed state.