-
Notifications
You must be signed in to change notification settings - Fork 243
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
[BUG] Failed to update pull secret on the disk #4036
Comments
@almightyyeh I can see in your config that you choose to skip daemon checks any particular reason for it? |
@praveenkumar Thanks for your reply ! I skip the preflight-checks about systemd with follow issue discuss: I have the same problem also. |
@almightyyeh even #3471 (comment) doesn't work in your case? |
@praveenkumar Yes, I had try resolution but still same situation with failed update pull-secret on disk. I’ll try newer version again later. |
with latest version, I am getting the same error with default config. ( OS : Ubuntu 22.04.2 LTS ) INFO Waiting until the user's pull secret is written to the instance disk... |
@gopaltirupur @almightyyeh Can you start crc with
|
@praveenkumar in my case, it pending until above 10 mins but without any error log message. |
Switched back to 2.33 ( latest is 2.34 ), Working now with out any issue, Thanks https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/crc/2.33.0 |
@gopaltirupur Thanks for sharing! @praveenkumar Thanks for update. I'll close the issue and switch new version. |
Is there any workaround if you want to use the latest version 2.34 to install OpenShift 4.15? I have the same issue |
the Issue occur in both two CRC version: crc-linux-2.19.0-amd64 & crc-linux-2.32.0-amd64.
General information
crc setup
before starting it (Yes)?CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
Actual
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f $ crc cleanup $ crc setup $ crc start --log-level debug above step had repeat serveral times with same problme.
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.The text was updated successfully, but these errors were encountered: