OKD-4.11 Cluster UPI on a bare metal : Failed for starting of kuber-apiserver #1358
Unanswered
biruand1016
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello
I am trying to install okd-4.11-2022-10-10-134119 cluster on bare metal with restricted network by using UPI
I am using 3 VMware Workstation vms on a dedicated server(AMD Ryzen 5 3600 6-Core Processor 3.60 GHz, 64GB RAM, 500GB HDD) for installing.
I got bootstrap install complete and cluster install complete, but I had the critical issue
$ openshift-install wait-for install-complete --dir dir
"Install complete!"
So, I logged in Openshift Web Console, and observed Administrator/Administration/Cluster Settings, and I noticed there is a error in update status part.
Error is
"This cluster should not be updated to the next minor version.
Cluster should not be upgraded between minor versions for multiple reasons: AdminAckRequired,DegradedPool
Kubernetes 1.25 and therefore OpenShift 4.12 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6955381 for details and instructions.
Cluster operator machine-config should not be upgraded between minor versions: One or more machine config pools are degraded, please see oc get mcp for further details and resolve before upgrading"
I had faced same issue in OKD-4.11.0-0.okd-20220820-02219
What is the reason of this issue?, How can I fix?
Testing conditions are following
I am using VMware NAT for networking
VMware Workstation NAT(Vmnet 8, 192.168.200.0/24, gateway 192.168.200.2, dhcp/dns disable)
This machine is needed for providing install command, and mirror registry, DNS, DHCP, HAproxy, HTTP.
spec : CentOS 8 Stream, CPU 2 cores, RAM 8G
spec : fedora-coreos-36.20220716.3.1-live.x86_64, CPU 4 cores, RAM 16G
spec: fedora-coreos-36.20220716.3.1-live.x86_64, CPU 4 cores, RAM 24G
Install workflow is
./openshift-install create manifests --dir /opt/okd
./openshift-install create ignition-configs --dir /opt/okd
I have installed FCOS ISO on bootstrap machine and applied bootstrap.iqn, and reboot the computer
I have installed FCOS ISO on master machine and applied master.iqn, and reboot the machine
./openshift-install --dir /opt/okd wait-for install-complete
"Install complete!"
I added install-config.yaml file and error file that contains some errors in my lab.
The main errors are
oc get operators
machine-api 4.11.0-0.okd-2022-10-10-134119 True False False 3h44m
machine-approver 4.11.0-0.okd-2022-10-10-134119 True False False 3h44m
machine-config True True True 3h25m Unable to apply 4.11.0-0.okd-2022-10-10-134119: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 1, ready 0, updated: 0, unavailable: 1)]
marketplace 4.11.0-0.okd-2022-10-10-134119 True False False 3h44m
oc get pods
openshift-kube-apiserver-operator kube-apiserver-operator-845f488949-nsn9n 1/1 Running 1 (82m ago) 86m
openshift-kube-apiserver installer-3-master0.ocd4.rnur.edu 0/1 Completed 0 81m
openshift-kube-apiserver installer-5-master0.ocd4.rnur.edu 0/1 Error 0 75m
openshift-kube-apiserver installer-5-retry-1-master0.ocd4.rnur.edu 0/1 Completed 0 71m
openshift-kube-apiserver kube-apiserver-master0.ocd4.rnur.edu 5/5 Running 0 70m
This pods all have "completed" Status and "0/1" Ready in web console
oc get mcp
oc get mcp
AME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
master False True True 1 0 0 1 86m
worker rendered-worker-23d70b843ba70bceb432bdfcb6c4021f True False False 0 0 0 0 86m
kube-apiserver-pod.log
error.log
install-config.yaml.txt
openshift_install.log
Beta Was this translation helpful? Give feedback.
All reactions