Closed YunWZ closed 7 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
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
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-bot: Closing this issue.
Version
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:
that output info:
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:
The outpu saying: mssing
/var/run/libvirt/libvirt-sock
So I created a symbol link :
the libvert version is:
References
N/A