Newbe OKD intall issues #1974

aheath1992 · 2024-07-17T16:03:35Z

aheath1992
Jul 17, 2024

I am trying to install OKD on top of libvirt in my home lab however I keep running into errors where when the networks are created on the control-plane nodes the HAProxy returns connection refused from the node. I am not sure what to troubleshoot form the control-plane side to see why connections are being refused, DNS is resolving, I can Ping the host from the bootstrap node and other nodes.
haproxy.txt

rvanderp3 · 2024-07-17T17:07:30Z

rvanderp3
Jul 17, 2024

I would try curling 22623 and 6443 on the bootstrap node. If you can't curl those, then I would check the bootstrap node journal for indications of why its not progressing. The control plane nodes will require the machine config server and API server to be up on the bootstrap node before an install will progress.

0 replies

aheath1992 · 2024-07-17T17:52:06Z

aheath1992
Jul 17, 2024
Author

So looking at the logs and curl commands i see the following:

[root@ns1 ~]# curl -k https://bootstrap.okd4.example.com:6443/
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "forbidden: User \"system:anonymous\" cannot get path \"/\"",
  "reason": "Forbidden",
  "details": {},
  "code": 403
}[root@ns1 ~]# curl -k https://bootstrap.okd4.example.com:22623/
[root@ns1 ~]# curl -k https://control-plane0.okd4.example.com:6443/
curl: (7) Failed to connect to control-plane0.okd4.example.com port 6443: Connection refused
[root@ns1 ~]# curl -k https://control-plane0.okd4.example.com:22623/
curl: (7) Failed to connect to control-plane0.okd4.example.com port 22623: Connection refused

I am able to curl from bootstrap node but not the control-plan0 node, not sure what to check or where to check for that,

On the bootstrap node I see this in the journalctl -b -f -u release-image.service -u bootkube.service that is standing out

Jul 17 17:47:43 okd4-bootstrap bootkube.sh[79927]: Starting cluster-bootstrap...
Jul 17 17:47:44 okd4-bootstrap bootkube.sh[80447]: Error: creating container storage: the container name "cluster-bootstrap" is already in use by 0cfe01c5b0368065d7c9ebeeffbf395e03f415b0845bd87bfcd67be61deada06. You have to remove that container to be able to reuse that name: that name is already in use, or use --replace to instruct Podman to do so.
Jul 17 17:47:44 okd4-bootstrap podman[80447]: 2024-07-17 17:47:44.001381368 +0000 UTC m=+0.015436481 image pull 4d019344c4e021dea21297252503e39108017c43a6f973d8ea936b861934ed4f quay.io/openshift/okd-content@sha256:9f3f8f11fd743a332f8328b774bed1854c5d5d058663eb122289191bcb0cee73
Jul 17 17:47:44 okd4-bootstrap bootkube.sh[79927]: Using /etc/kubernetes/bootstrap-secrets/kubeconfig as KUBECONFIG
Jul 17 17:47:44 okd4-bootstrap bootkube.sh[79927]: Gathering cluster resources ...
Jul 17 17:47:44 okd4-bootstrap sudo[80460]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get nodes -o jsonpath --template '{range .items[*]}{.metadata.name}{"\\n"}{end}'
Jul 17 17:47:44 okd4-bootstrap sudo[80464]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get nodes -o jsonpath -l node-role.kubernetes.io/master --template '{range .items[*]}{.metadata.name}{"\\n"}{end}'
Jul 17 17:47:44 okd4-bootstrap sudo[80472]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get pods -l apiserver=true --all-namespaces --template '{{ range .items }}-n {{ .metadata.namespace }} {{ .metadata.name }}{{ "\\n" }}{{ end }}'
Jul 17 17:47:44 okd4-bootstrap sudo[80468]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get pods --all-namespaces --template '{{ range .items }}{{ $name := .metadata.name }}{{ $ns := .metadata.namespace }}{{ range .spec.containers }}-n {{ $ns }} {{ $name }} -c {{ .name }}{{ "\\n" }}{{ end }}{{ range .spec.initContainers }}-n {{ $ns }} {{ $name }} -c {{ .name }}{{ "\\n" }}{{ end }}{{ end }}'
Jul 17 17:47:44 okd4-bootstrap sudo[80476]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get apiservices -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80480]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get clusteroperators -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80460]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80484]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get clusterversion -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80464]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80488]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get configmaps --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80506]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get events --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80493]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get csr -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80498]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get endpoints --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80472]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80468]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80515]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get kubeapiserver -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80476]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80519]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get kubecontrollermanager -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80480]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80484]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80523]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get machines --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80506]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80488]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80529]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get machineconfigpools -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80541]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get machineconfigs -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80576]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get openshiftapiserver -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80493]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80498]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80546]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80515]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80562]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get nodes -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80600]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get roles --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80519]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80580]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get pods --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80523]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80591]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get rolebindings --all-namespaces -o json
Jul 17 17:47:44 okd4-bootstrap sudo[80529]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80604]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get secrets --all-namespaces
Jul 17 17:47:44 okd4-bootstrap sudo[80620]:     root : PWD=/var/opt/openshift ; USER=root ; ENV=KUBECONFIG=/etc/kubernetes/bootstrap-secrets/kubeconfig ; COMMAND=/usr/bin/oc --request-timeout=5s get secrets --all-namespaces -o=custom-columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,TYPE:.type,ANNOTATIONS:.metadata.annotations
Jul 17 17:47:44 okd4-bootstrap sudo[80576]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80541]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80546]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80562]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80600]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80580]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80591]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80604]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap sudo[80620]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jul 17 17:47:44 okd4-bootstrap systemd[1]: bootkube.service: Main process exited, code=exited, status=1/FAILURE
Jul 17 17:47:44 okd4-bootstrap systemd[1]: bootkube.service: Failed with result 'exit-code'.
Jul 17 17:47:44 okd4-bootstrap systemd[1]: bootkube.service: Consumed 2.053s CPU time.
Jul 17 17:47:44 okd4-bootstrap sudo[80460]: pam_unix(sudo:session): session closed for user root
Jul 17 17:47:44 okd4-bootstrap sudo[80460]: PAM Attempted to close sd-bus after fork, this should not happen.
Jul 17 17:47:44 okd4-bootstrap sudo[80464]: pam_unix(sudo:session): session closed for user root
Jul 17 17:47:44 okd4-bootstrap sudo[80464]: PAM Attempted to close sd-bus after fork, this should not happen.

HAProxy is showing that it can connect to the bootstrap node but not control-plane0

Jul 17 13:30:34 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for backup server api-server-6443/bootstrap succeeded, reason: Layer7 check passed, code: 200, check duration: 3ms, status: 1/3 DOWN.
Jul 17 13:30:44 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for backup server api-server-6443/bootstrap succeeded, reason: Layer7 check passed, code: 200, check duration: 4ms, status: 2/3 DOWN.
Jul 17 13:30:54 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for backup server api-server-6443/bootstrap succeeded, reason: Layer7 check passed, code: 200, check duration: 3ms, status: 2/2 UP.
Jul 17 13:30:54 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Backup Server api-server-6443/bootstrap is UP. 0 active and 1 backup servers online. Running on backup. 0 sessions requeued, 0 total in queue.
Jul 17 13:33:58 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for server api-server-6443/control-plane0 failed, reason: Layer4 timeout, check duration: 10001ms, status: 0/3 DOWN.
Jul 17 13:34:08 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for server api-server-6443/control-plane0 failed, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms, status: 0/3 DOWN.
Jul 17 13:34:23 ns1.example.com haproxy[1015]: [WARNING]  (1015) : Health check for server api-server-6443/control-plane2 failed, reason: Layer4 timeout, check duration: 10000ms, status: 0/3 DOWN.

0 replies

rvanderp3 · 2024-07-17T18:41:50Z

rvanderp3
Jul 17, 2024

so the bootstrap is up and serving the mcs and the api, thats good. can you paste a screen shot from the console on one of the control plane nodes? also, if you happen to log bundle from the failed install that would be helpful as well.

0 replies

aheath1992 · 2024-07-17T20:09:55Z

aheath1992
Jul 17, 2024
Author

Not sure what logs would be helpful, but it seems I keep going backwards, now my bootstrap node is not bringing up the API server and im seeing the following in the kubelet.service journal

Jul 17 20:07:47 bootstrap kubelet.sh[75163]: E0717 20:07:47.454430   75163 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-apiserver\" with CrashLoopBackOff: \"back-off 1m20s restarting failed container=kube-apiserver pod=bootstrap-kube-apiserver-bootstrap_openshift-kube-apiserver(69687cb57a65df529c1f3e1ebcbf8b47)\"" pod="openshift-kube-apiserver/bootstrap-kube-apiserver-bootstrap" podUID="69687cb57a65df529c1f3e1ebcbf8b47"

0 replies

rvanderp3 · 2024-07-17T20:16:34Z

rvanderp3
Jul 17, 2024

these are the logs that are needed if you can get them:
https://docs.okd.io/4.16/installing/installing-troubleshooting.html

0 replies

aheath1992 · 2024-07-17T20:38:12Z

aheath1992
Jul 17, 2024
Author

Here are the logs from the bootstrap node and the one current master

log-bundle-20240717163640.tar.gz

0 replies

aheath1992 · 2024-07-18T16:16:11Z

aheath1992
Jul 18, 2024
Author

So the main issue I am seeing in the logs and journal currently is

Jul 18 16:14:48 bootstrap bootkube.sh[3725]: [#1751] failed to fetch discovery: Get "https://localhost:6443/api?timeout=32s": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-07-18T16:14:48Z is after 2024-07-17T17:19:21Z
Jul 18 16:14:49 bootstrap cluster-bootstrap[3778]: [#1752] failed to fetch discovery: Get "https://localhost:6443/api?timeout=32s": dial tcp [::1]:6443: connect: connection refused - error from a previous attempt: read tcp [::1]:60928->[::1]:6443: read: connection reset by peer
Jul 18 16:14:49 bootstrap bootkube.sh[3725]: [#1752] failed to fetch discovery: Get "https://localhost:6443/api?timeout=32s": dial tcp [::1]:6443: connect: connection refused - error from a previous attempt: read tcp [::1]:60928->[::1]:6443: read: connection reset by peer
Jul 18 16:14:50 bootstrap cluster-bootstrap[3778]: [#1753] failed to fetch discovery: Get "https://localhost:6443/api?timeout=32s": dial tcp [::1]:6443: connect: connection refused
Jul 18 16:14:50 bootstrap bootkube.sh[3725]: [#1753] failed to fetch discovery: Get "https://localhost:6443/api?timeout=32s": dial tcp [::1]:6443: connect: connection refused

I have Gathered logs for analysis:
log-bundle-20240718121230.tar.gz

0 replies

rvanderp3 · 2024-07-18T18:19:03Z

rvanderp3
Jul 18, 2024

You very possibly have old certificates based on the expiration warning above. I would recommend you delete the current directory where your ignition files are being generated and try again. Stale content can remain in that directory between installation attempts.

0 replies

aheath1992 · 2024-07-18T19:54:42Z

aheath1992
Jul 18, 2024
Author

Ok got the cert issue resolved now i have the cluster doing something, i see errors on control-plane0 as follows:

Jul 18 19:48:54 control-plane0.okd4.example.com kubenswrapper[2534]: E0718 19:48:54.530959    2534 pod_workers.go:1300] "Error syncing pod, skipping" err="network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: No CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?" pod="openshift-network-diagnostics/network-check-target-6j2cn" podUID="55eb4de5-966f-4211-aec3-050535e0d095"

However this node is able to communicate and is presenting an API that HAProxy is able to communicate with but also odd it's saying that node is not ready while the other 2 are. Not sure what's going on with that

NAME                              STATUS     ROLES                  AGE   VERSION
control-plane0.okd4.example.com   NotReady   control-plane,master   54m   v1.28.7+6e2789b
control-plane1.okd4.example.com   Ready      control-plane,master   50m   v1.28.7+6e2789b
control-plane2.okd4.example.com   Ready      control-plane,master   50m   v1.28.7+6e2789b

I have collected logs to maybe better help
log-bundle-20240718154932.tar.gz

0 replies

rvanderp3 · 2024-07-19T14:07:16Z

rvanderp3
Jul 19, 2024

I suspect there may be an overcommitment or storage issue. etcd is taking over 10s(should be < 200ms) to read. so I think your cluster will eventually finish installing if you just wait, but your cluster probably won't be as responsive as you'd like.

{"level":"warn","ts":"2024-07-18T19:39:06.458793Z","caller":"etcdserver/util.go:170","msg":"apply request took too long","took":"10.669075005s","expected-duration":"200ms","prefix":"read-only range ","request":"key:"/kubernetes.io/console.openshift.io/consolesamples/" range_end:"/kubernetes.io/console.openshift.io/consolesamples0" limit:10000 ","response":"","error":"etcdserver: leader changed"}

0 replies

aheath1992 · 2024-07-19T15:13:32Z

aheath1992
Jul 19, 2024
Author

So it looks like its been here for the past hour, not sure if their is something I can do to help clean up these errors and help the installer move on or not:

authentication                             4.15.0-0.okd-2024-03-10-010116   False       True          True       109m    OAuthServerServiceEndpointAccessibleControllerAvailable: Get "https://172.30.184.110:443/healthz": dial tcp 172.30.184.110:443: connect: connection refused...
baremetal                                  4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
cloud-controller-manager                   4.15.0-0.okd-2024-03-10-010116   True        False         False      115m    
cloud-credential                           4.15.0-0.okd-2024-03-10-010116   True        False         False      117m    
cluster-autoscaler                         4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
config-operator                            4.15.0-0.okd-2024-03-10-010116   True        False         False      109m    
console                                                                                                                  
control-plane-machine-set                  4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
csi-snapshot-controller                    4.15.0-0.okd-2024-03-10-010116   True        True          False      56m     CSISnapshotControllerProgressing: Waiting for Deployment to deploy pods
dns                                        4.15.0-0.okd-2024-03-10-010116   True        False         False      107m    
etcd                                       4.15.0-0.okd-2024-03-10-010116   True        True          True       106m    NodeInstallerDegraded: 1 nodes are failing on revision 6:...
image-registry                             4.15.0-0.okd-2024-03-10-010116   True        True          False      34m     Progressing: All registry resources are removed...
ingress                                                                     False       True          True       108m    The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.0-0.okd-2024-03-10-010116   True        False         False      103m    
kube-apiserver                             4.15.0-0.okd-2024-03-10-010116   False       True          True       109m    StaticPodsAvailable: 0 nodes are active; 3 nodes are at revision 0; 0 nodes have achieved new revision 8
kube-controller-manager                    4.15.0-0.okd-2024-03-10-010116   False       True          True       109m    StaticPodsAvailable: 0 nodes are active; 3 nodes are at revision 0; 0 nodes have achieved new revision 7
kube-scheduler                             4.15.0-0.okd-2024-03-10-010116   True        True          True       34m     NodeInstallerDegraded: 1 nodes are failing on revision 7:...
kube-storage-version-migrator              4.15.0-0.okd-2024-03-10-010116   False       True          False      43m     KubeStorageVersionMigratorAvailable: Waiting for Deployment
machine-api                                4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
machine-approver                           4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
machine-config                             4.15.0-0.okd-2024-03-10-010116   False       False         True       25m     Cluster not available for [{operator 4.15.0-0.okd-2024-03-10-010116}]: error during waitForDeploymentRollout: [context deadline exceeded, deployment machine-config-controller is not ready. status: (replicas: 1, updated: 1, ready: 0, unavailable: 1)]
marketplace                                4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
monitoring                                                                  False       True          True       50m     UpdatingAlertmanager: reconciling Alertmanager Route failed: retrieving Route object failed: the server is currently unable to handle the request (get routes.route.openshift.io alertmanager-main), UpdatingConsolePluginComponents: reconciling Console Plugin failed: creating ConsolePlugin object failed: the server could not find the requested resource (post consoleplugins.console.openshift.io), UpdatingUserWorkloadThanosRuler: deleting Thanos Ruler Route failed: the server is currently unable to handle the request (delete routes.route.openshift.io thanos-ruler), UpdatingThanosQuerier: reconciling Thanos Querier Route failed: retrieving Route object failed: the server is currently unable to handle the request (get routes.route.openshift.io thanos-querier), UpdatingUserWorkloadPrometheus: deleting UserWorkload federate Route failed: the server is currently unable to handle the request (delete routes.route.openshift.io federate), UpdatingPrometheus: reconciling Prometheus API Route failed: retrieving Route object failed: the server is currently unable to handle the request (get routes.route.openshift.io prometheus-k8s), UpdatingPrometheus: prometheuses.monitoring.coreos.com "k8s" not found
network                                    4.15.0-0.okd-2024-03-10-010116   True        True          False      110m    DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)...
node-tuning                                4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
openshift-apiserver                        4.15.0-0.okd-2024-03-10-010116   True        True          False      13m     APIServerDeploymentProgressing: deployment/apiserver.openshift-apiserver: 1/3 pods have been updated to the latest generation
openshift-controller-manager               4.15.0-0.okd-2024-03-10-010116   True        True          False      104m    Progressing: deployment/controller-manager: updated replicas is 1, desired replicas is 3...
openshift-samples                                                                                                        
operator-lifecycle-manager                 4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
operator-lifecycle-manager-catalog         4.15.0-0.okd-2024-03-10-010116   True        False         False      108m    
operator-lifecycle-manager-packageserver                                    False       True          False      108m    ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: InstallCheckFailed, message: install timeout
service-ca                                 4.15.0-0.okd-2024-03-10-010116   True        True          False      109m    Progressing: ...
storage

log-bundle-20240719122954.tar.gz

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Newbe OKD intall issues #1974

{{title}}

Replies: 11 comments

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Newbe OKD intall issues #1974

aheath1992 Jul 17, 2024

Replies: 11 comments

rvanderp3 Jul 17, 2024

aheath1992 Jul 17, 2024 Author

rvanderp3 Jul 17, 2024

aheath1992 Jul 17, 2024 Author

rvanderp3 Jul 17, 2024

aheath1992 Jul 17, 2024 Author

aheath1992 Jul 18, 2024 Author

rvanderp3 Jul 18, 2024

aheath1992 Jul 18, 2024 Author

rvanderp3 Jul 19, 2024

aheath1992 Jul 19, 2024 Author

aheath1992
Jul 17, 2024

rvanderp3
Jul 17, 2024

aheath1992
Jul 17, 2024
Author

rvanderp3
Jul 17, 2024

aheath1992
Jul 17, 2024
Author

rvanderp3
Jul 17, 2024

aheath1992
Jul 17, 2024
Author

aheath1992
Jul 18, 2024
Author

rvanderp3
Jul 18, 2024

aheath1992
Jul 18, 2024
Author

rvanderp3
Jul 19, 2024

aheath1992
Jul 19, 2024
Author