openshift / installer

Install an OpenShift 4.x cluster
https://try.openshift.com
Apache License 2.0
1.44k stars 1.38k forks source link

Install OpenShift4.12 on baremetal failed. #7603

Closed YunWZ closed 7 months ago

YunWZ commented 1 year ago

Version

[kni@fedora ~]$ ./openshift-baremetal-install version
./openshift-baremetal-install 4.12.36
built from commit 9520d1dde4b11f906504b259da44ec29fa1d5e43
release image quay.io/openshift-release-dev/ocp-release@sha256:38ccab25d5895a216a465a9f297541fbbebe7aa115fdaa9f2015c8d5a5d036eb
release architecture amd64

Platform:

Provisionor: Fedora release 38 (Thirty Eight)/ 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz Baremetal: 3 x H3C R4900 R3

Deploy openshift through IPI

What happened?

I try to deploy openshift4 on baremetal( 3 nodes). Refer to okd install doc: https://docs.okd.io/4.12/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html

When I executed cmd:

./openshift-baremetal-install --dir ~/clusterconfigs --log-level debug create cluster

that output info:

DEBUG [INFO] running Terraform command: /home/kni/clusterconfigs/terraform/bin/terraform apply -no-color -auto-approve -input=false -var-file=/tmp/openshift-install-bootstrap-610941851/terraform.tfvars.json -var-file=/tmp/openshift-install-bootstrap-610941851/terraform.platform.auto.tfvars.json -lock=true -parallelism=10 -refresh=true
ERROR
ERROR Error: failed to connect: xdr:DecodeUint: EOF while decoding 4 bytes - read: '[]'
ERROR
ERROR   with provider["openshift/local/libvirt"],
ERROR   on main.tf line 1, in provider "libvirt":
ERROR    1: provider "libvirt" {
ERROR
ERROR failed to fetch Cluster: failed to generate asset "Cluster": failure applying terraform for "bootstrap" stage: failed to create cluster: failed to apply Terraform: exit status 1
ERROR
ERROR Error: failed to connect: xdr:DecodeUint: EOF while decoding 4 bytes - read: '[]'
ERROR
ERROR   with provider["openshift/local/libvirt"],
ERROR   on main.tf line 1, in provider "libvirt":
ERROR    1: provider "libvirt" {
ERROR
ERROR

What you expected to happen?

Cluster created successfully.

How to reproduce it (as minimally and precisely as possible)?

Refer to okd install doc: https://docs.okd.io/4.12/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html

Anything else we need to know?

Before the above error, there was another error:

./openshift-baremetal-install --dir ~/clusterconfigs --log-level debug create cluster

The outpu saying: mssing /var/run/libvirt/libvirt-sock

So I created a symbol link :

ln -s /var/run/libvirt/libvirt-admin-sock /var/run/libvirt/libvirt-sock

the libvert version is:

[kni@fedora libvirt]$ libvirtd -V
libvirtd (libvirt) 9.0.0

References

N/A

openshift-bot commented 9 months ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 8 months ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 7 months ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 7 months ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/installer/issues/7603#issuecomment-2002352366): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.