-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying of OCP4.6 with faros failing #175
Comments
I executed the following commands to restart the cluster install and the behavior is different now, farosctl apply Now the installation is hanging at following step, STEP 7: CREATE THE BOOTSTRAP NODE And looks like bootstarp vm doesn't show any error, Red Hat Enterprise Linux CoreOS 47.83.202103251640-0 (Ootpa) 4.7 And it fails with following error message, STEP 8: WAIT FOR THE OPENSHIFT INSTALLATION TO COMPLETE create cluster Failed |
Hi Ryan,
I am trying to deploy OCP4.6 with faros, and i created following link for farosctl to pin the version to 4.6.
[farosadmin@bastion bin]$ pwd
/home/farosadmin/bin
[farosadmin@bastion bin]$ ll farosctl.4.6
lrwxrwxrwx. 1 farosadmin farosadmin 8 Aug 23 10:17 farosctl.4.6 -> farosctl
[farosadmin@bastion bin]$
And deploying the cluster with following command,
[farosadmin@bastion ~]$ farosctl.4.6 install-plan cluster
The deployment is stuck at following step,
|
|-- create cluster
|
STEP 1: PERFORM PRE-INSTALL CHECKS
STEP 2: ENSURE ALL CLUSTER NODES ARE POWERED DOWN
management : power off kvm server power state 192.168.139.1>bootstrap
STEP 3: ENSURE ALL CLUSTER NODES ARE POWERED DOWN
management : power off ilo server power state blade-5
STEP 4: ENSURE ALL CLUSTER NODES ARE POWERED DOWN
management : power off ilo server power state blade-1
STEP 5: ENSURE ALL CLUSTER NODES ARE POWERED DOWN
management : power off ilo server power state blade-3
STEP 6: CREATE THE CONTROL PLANE
management : network boot ilo servers blade-1 blade-3 blade-5
STEP 7: CREATE THE BOOTSTRAP NODE
management : network boot kvm servers 192.168.139.1>bootstrap
wait for bootstrap to finish provisioning:
And when i check the bootstap vm console, i see following error.
Displaying logs from failed units: ignition-fetch-offline.service
-- Logs begin at Tue 2021-08-24 16:47:54 UTC, end at Tue 2021-08-24 16:47:56 UTC. --
Aug 24 16:47:56 ignition[680]: parsing config with SHA512: ff6a5153be363997e4d5d3ea8cc4048373a457c48c4a5b134a08a30aacd167c1e0f099f0bdf1e24c99ad180628cd02b767b863b5fe3a8fce3fe1886847eb8e2e
Aug 24 16:47:56 systemd[1]: Failed to start Ignition (fetch-offline).
Aug 24 16:47:56 ignition[680]: parsed url from cmdline: ""
Aug 24 16:47:56 ignition[680]: no config URL provided
Aug 24 16:47:56 ignition[680]: reading system config file "/usr/lib/ignition/user.ign"
Aug 24 16:47:56 ignition[680]: parsing config with SHA512: e9bd0629fae3427c71482de3f5486aceb0d7bb135ae21b4673442fcb26076a7699b1db2272f57f16c9c3bafba6cb15881a033999a4c77131b797182c114c18dc
Aug 24 16:47:56 ignition[680]: failed to fetch config: unsupported config version
Aug 24 16:47:56 ignition[680]: failed to acquire config: unsupported config version
Aug 24 16:47:56 systemd[1]: ignition-fetch-offline.service: Triggering OnFailure= dependencies.
Aug 24 16:47:56 ignition[680]: Ignition failed: unsupported config version
Press Enter for emergency shell or wait 0 minutes 30 seconds for reboot.
Please let me know what could be the reason for this error on bootstrap node ?
The text was updated successfully, but these errors were encountered: