search

project-faros / cluster-manager

The meat and potatoes behind farosctl
GNU General Public License v3.0
13 stars 6 forks source link

Deploying OCP 4.8.4 is failing #178

Open VishnuPriya777 opened 3 years ago

VishnuPriya777 commented 3 years ago

Hi,

We are trying to deploy OCP 4.8.4 and facing issues with live rootfs image. I have attached the screenshot below.

Capture10 Capture11

Able to login to bootstrap machine but cluster creation is getting failed.

Capture12

Please let me know if more details required.

VishnuPriya777 commented 3 years ago

error:-

wait for bootstrap to complete failed: localhost: non-zero return code there was an error during install failed: localhost: level=info msg=Waiting up to 20m0s for the Kubernetes API at https://api.faros.tennet.local:6443... level=info msg=API v1.21.1+d8043e1 up level=info msg=Waiting up to 30m0s for bootstrapping to complete... W1001 09:46:09.675370 624 reflector.go:436] k8s.io/client-go/tools/watch/informerwatcher.go:146: watch of v1.ConfigMap ended with: very short watch: k8s.io/client-go/tools/watch/informerwatcher.go:146: Unexpected watch close - watch lasted less than a second and no items received W1001 10:06:25.728024 624 reflector.go:436] k8s.io/client-go/tools/watch/informerwatcher.go:146: watch of v1.ConfigMap ended with: very short watch: k8s.io/client-go/tools/watch/informerwatcher.go:146: Unexpected watch close - watch lasted less than a second and no items received level=info msg=Use the following commands to gather logs from the cluster level=info msg=openshift-install gather bootstrap --help level=error msg=Bootstrap failed to complete: timed out waiting for the condition level=error msg=Failed to wait for bootstrapping to complete. This error usually happens when there is a problem with control plane hosts that prevents the control plane operators from creating the control plane. level=fatal msg=Bootstrap failed to complete

create cluster Failed

VishnuPriya777 commented 3 years ago

Hi Team,

Could you please provide update on this?

rmkraus commented 3 years ago

Sorry for the delay, I have been OOO this past week.

It looks like there is an issue with the DNS server that is running on the bastion node. From the bastion node, try running dig @localhost quay.io. You may need to install dig using dnf.

From there, ensure the named service is running on the bastion.

Also, there may be a better way for us to get you help. Are you a Red Hat customer, employee, or an HPE employee?