crc
crc copied to clipboard
crc-org
Updating to 2.48 doesn't update daemon (The executable version (2.48.0) doesn't match the daemon version (2.47.0))
General information
I've updated OpenShift Local to 2.48 through the podman extension. When I try to start Microshift I get:
PS C:\Users\grove> crc start
The executable version (2.48.0) doesn't match the daemon version (2.47.0)
A crc setup did not fix things. Pressing "Initialize & Start" in the extension also didn't fix things.
Possibly relevant: I don't remember for certain, but I think I originally installed crc through the installer one can download through the Red Hat portal, not Podman.
I can of course delete & reinstall, but figured I'd leave the system in this state to help troubleshoot, to help other users who might experience the same issue.
Operating System
Windows
Hypervisor
Hyper-V
Did you run crc setup before crc start?
yes
Running on
Laptop
Steps to reproduce
- Install, setup, and start 2.47.0 (potentially through the regular installer)
- See the update notification in the podman extension, click the button to update
- Try to run
crc start(or initializing & running through the podman extension)
CRC version
CRC version: 2.48.0+1aa46c
OpenShift version: 4.18.1
MicroShift version: 4.18.1
CRC status
DEBU CRC version: 2.48.0+1aa46c
DEBU OpenShift version: 4.18.1
DEBU MicroShift version: 4.18.1
DEBU Running 'crc status'
CRC VM: Stopped
MicroShift: Stopped (v4.17.14)
Disk Usage: 0B of 0B (Inside the CRC VM)
Persistent Volume Usage: 0B of 0B (Allocated)
Cache Usage: 11.71GB
Cache Directory: C:\Users\grove\.crc\cache
CRC config
- consent-telemetry : no
- preset : microshift
Host Operating System
Host Name: GROVE
OS Name: Microsoft Windows 11 Enterprise
OS Version: 10.0.26100 N/A Build 26100
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Product ID: 00329-10280-00000-AA469
Original Install Date: 28/02/2025, 09:02:22
System Boot Time: 28/02/2025, 10:10:22
System Manufacturer: Dell Inc.
System Model: XPS 16 9640
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 170 Stepping 4 GenuineIntel ~2300 Mhz
BIOS Version: Dell Inc. 1.11.1, 24/12/2024
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Total Physical Memory: 64.981 MB
Available Physical Memory: 33.786 MB
Virtual Memory: Max Size: 74.709 MB
Virtual Memory: Available: 39.254 MB
Virtual Memory: In Use: 35.455 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Hotfix(s): 3 Hotfix(s) Installed.
[01]: KB5049622
[02]: KB5051987
[03]: KB5052085
Network Card(s): 6 NIC(s) Installed.
[01]: Wintun Userspace Tunnel
Connection Name: OpenVPN Wintun
Status: Media disconnected
[02]: TAP-Windows Adapter V9
Connection Name: Local Area Connection
DHCP Enabled: Yes
DHCP Server: 10.8.64.25
IP address(es)
[01]: 10.8.64.26
[02]: fe80::82c6:d9a8:6ea5:c632
[03]: OpenVPN Data Channel Offload
Connection Name: OpenVPN Data Channel Offload
Status: Media disconnected
[04]: Intel(R) Wi-Fi 7 BE200 320MHz
Connection Name: Wi-Fi
DHCP Enabled: Yes
DHCP Server: 172.26.128.91
IP address(es)
[01]: 192.168.5.77
[02]: fe80::e30c:6183:87d8:7e7b
[05]: DisplayLink Network Adapter NCM
Connection Name: Ethernet 2
DHCP Enabled: Yes
DHCP Server: 255.255.255.255
IP address(es)
[01]: 169.254.180.181
[02]: fe80::d91e:7536:724:d5c0
[06]: Bluetooth Device (Personal Area Network)
Connection Name: Bluetooth Network Connection
Status: Media disconnected
Virtualization-based security: Status: Running
Required Security Properties:
Available Security Properties:
Base Virtualization Support
DMA Protection
UEFI Code Readonly
SMM Security Mitigations 1.0
Mode Based Execution Control
APIC Virtualization
Services Configured:
Hypervisor enforced Code Integrity
Services Running:
Credential Guard
Hypervisor enforced Code Integrity
Hypervisor-Enforced Paging Translation
App Control for Business policy: Enforced
App Control for Business user mode policy: Off
Security Features Enabled:
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Expected behavior
I expect the upgrade to go seamlessly, allowing me to start Microshift again.
Actual behavior
Microshift won't start again because the daemon isn't updated
CRC Logs
DEBU CRC version: 2.48.0+1aa46c
DEBU OpenShift version: 4.18.1
DEBU MicroShift version: 4.18.1
DEBU Running 'crc start'
DEBU Total memory of system is 68137205760 bytes
DEBU No new version available. The latest version is 2.48.0
DEBU Machine: libhvee -> state
DEBU Machine: libhvee -> get machine
DEBU Machine: libhvee -> state: get
DEBU Machine: libhvee -> state: stopped
The executable version (2.48.0) doesn't match the daemon version (2.47.0)
Additional context
I have not ran crc delete -f yet.
@Grovespaz from the cli can you try crc cleanup => crc setup and the crc start and let us know if that fix it?
Originally crc cleanup failed with:
C:\Users\gover> crc cleanup
INFO Removing the daemon task
INFO Removing the win32 background launcher
INFO Stop daemon process if it is running
INFO Removing crc's virtual machine
INFO Removing CRC manpages
INFO Removing CRC Specific entries from user's known_hosts file
INFO Removing hosts file records added by CRC
INFO Removing pull secret from the keyring
INFO Removing older logs
Failed to remove old log files: Failed to delete file: remove C:\Users\gover\.crc\crcd.log: The process cannot access the file because it is being used by another process.
There was an errant crc.exe process still running, even though there shouldn't have been because nothing was still open. I killed it and proceeded. (I mention it because it may be relevant to how the update failed?)
Afterwards, all commands ran succesfully and microshift is running again.
@Grovespaz do you by any chance have the crc setup logs (in your terminal buffer; as cleanup removes the log file) from before the issue was fixed, curious to see what it detects, as we have code to check if an older version of the daemon is running in https://github.com/crc-org/crc/blob/4bdcc16077a84583ad85ea5b8b75eefab13ba82d/pkg/crc/preflight/preflight_daemon_task_check_windows.go#L82
@anjannath I do!
PS C:\Users\grove> crc setup
INFO Using bundle path C:\Users\grove\.crc\cache\crc_microshift_hyperv_4.18.1_amd64.crcbundle
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: C:\Users\grove\.crc\bin\oc
INFO Checking if running in a shell with administrator rights
INFO Checking Windows release
INFO Checking Windows edition
INFO Checking if Hyper-V is installed and operational
INFO Checking if Hyper-V service is enabled
INFO Checking if crc-users group exists
INFO Checking if current user is in crc-users and Hyper-V admins group
INFO Checking if vsock is correctly configured
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if C:\Users\grove\.crc\cache\crc_microshift_hyperv_4.18.1_amd64.crcbundle exists
INFO Getting bundle for the CRC executable
INFO Downloading bundle: C:\Users\grove\.crc\cache\crc_microshift_hyperv_4.18.1_amd64.crcbundle...
900.00 MiB / 1.39 GiB [----------------------------------------------------->______________________________] 63.13% 1.78 MiB1.39 GiB / 1.39 GiB [----------------------------------------------------------------------------------] 100.00% 1.78 MiB/s
INFO Uncompressing C:\Users\grove\.crc\cache\crc_microshift_hyperv_4.18.1_amd64.crcbundle
crc.vhdx: 4.07 GiB / 4.07 GiB [----------------------------------------------------------------------------------] 100.00%
oc.exe: 141.28 MiB / 141.28 MiB [--------------------------------------------------------------------------------] 100.00%
INFO Checking if the win32 background launcher is installed
INFO Checking if the daemon task is installed
INFO Installing the daemon task
INFO Checking if the daemon task is running
INFO Running the daemon task
INFO Checking admin helper service is running
INFO Checking SSH port availability
Your system is correctly setup for using CRC. Use 'crc start' to start the instance
PS C:\Users\grove> crc start
The executable version (2.48.0) doesn't match the daemon version (2.47.0)
@Grovespaz tried upgrading to 2.48.0 from 2.47.0 and after crc setup 2.48.0 daemon was running.
from your logs also it seems crc setup was installing the new daemon and there were no errors, my guess is somehow the previous daemon service didn't stop, let us know if you face this issue again on the next update