Skip to content
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

Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk #4165

Closed
OlGe404 opened this issue May 15, 2024 · 3 comments
Labels

Comments

@OlGe404
Copy link

OlGe404 commented May 15, 2024

I'm trying to get CRC 2.34.1 working on my local machine, but it fails with Failed to update pull secret on the disk: Temporary error: pull secret not updated to disk. I also tested with the latest CRC release (2.36.0 at the time of writing).

# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
VERSION="22.04.4 LTS (Jammy Jellyfish)"

I followed the installation instructions and used sudo apt-get update && sudo apt install -y qemu-kvm libvirt-daemon libvirt-daemon-system network-manager to install the prerequisites. My user is part of the libvirt group etc.

I then proceeded with these commands to get crc up and running:

crc setup
crc config set kubeadmin-password kubeadmin
crc config set pull-secret-file $(pwd)/pull-secret.json
crc start

After it failed, I used SSH to connect to the instance and found this:

$ ssh -i ~/.crc/machines/crc/id_ecdsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null  [email protected]
...
[systemd]
Failed Units: 1
  qemu-guest-agent.service
...

[core@crc ~]$ systemctl status qemu-guest-agent.service
× qemu-guest-agent.service - QEMU Guest Agent
     Loaded: loaded (/etc/systemd/system/qemu-guest-agent.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-05-15 06:21:40 UTC; 13min ago
   Duration: 5ms
   Main PID: 936 (code=exited, status=1/FAILURE)
        CPU: 4ms

May 15 06:21:40 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 5.
May 15 06:21:40 crc systemd[1]: Stopped QEMU Guest Agent.
May 15 06:21:40 crc systemd[1]: qemu-guest-agent.service: Start request repeated too quickly.
May 15 06:21:40 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
May 15 06:21:40 crc systemd[1]: Failed to start QEMU Guest Agent.

[core@crc ~]$ journalctl -u qemu-guest-agent.service

Mar 26 03:42:05 crc systemd[1]: Started QEMU Guest Agent.
Mar 26 03:42:05 crc qemu-ga[955]: 1711424525.300325: critical: Failed to create socket: Address family not supported by protocol
Mar 26 03:42:05 crc qemu-ga[955]: 1711424525.300341: critical: failed to create guest agent channel
Mar 26 03:42:05 crc qemu-ga[955]: 1711424525.300346: critical: failed to initialize guest agent channel
Mar 26 03:42:05 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 03:42:05 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
lines 1-14

I tried to fix this with sudo systemctl restart libvirtd on my local machine, but without success.

I attached the ~/.crc/crc.logfile.
crc.log

Any ideas on how to resolve this? I'd really like to use CRC for my local development and testing, since we use OCP 4 at work and I want to evaluate if our local developers could use it.

KInd regards,
Oliver

@anjannath
Copy link
Member

anjannath commented May 15, 2024

From the logs it seems you didn't run the 2.36.0 version which has the fix for the issue you are facing.

After downloading the new release, please use the following steps, to start from a clean environment:

$ crc delete -f # will delete the existing crc VM from 2.34.1 version 
$ crc setup --log-level debug
$ crc start --log-level debug

and the error about qemu-guest-agent service not running can be safely ignored

@OlGe404
Copy link
Author

OlGe404 commented May 15, 2024

Hi anjannath,

thank you for the response. I deleted the crc instance as you suggested and re-downloaded all the files for version 2.36.0 - now it seems to work. I'm sure that I tested with 2.36.0, but maybe I was missing the "-f" flag when deleting the crc instance ¯_(ツ)_/¯

What was the issue here? I'd like to be able to understand it so I can troubleshoot it next time. Anyways, you can close this ticket IMO.

Thank you for the fast response.

Kind regards,
Oliver

@praveenkumar
Copy link
Member

What was the issue here?

#4110 have all the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants