crc: Corrupt bundles are not overwritten by `crc setup`
General information
- OS: Linux (Fedora 30)
- Hypervisor: KVM
- Did you run
crc setupbefore starting it (Yes/No)? Yes
CRC version
# [asimha@asimha-fedora crc-linux-1.0.0-rc.0-amd64]$ crc version
version: 1.0.0-rc.0+34371d3
OpenShift version: 4.2.0-0.nightly-2019-09-26-192831 (embedded in binary)
CRC status
# Put `crc status` output here
CRC config
# Put `crc config view` output here
Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows
[asimha@asimha-fedora Downloads]$ cat /etc/redhat-release Fedora release 30 (Thirty)
Steps to reproduce
- Download CRC and pull-secret.txt
- run crc setup
- run crc start
Expected
complete without errors
Actual
[asimha@asimha-fedora crc-linux-1.0.0-rc.0-amd64]$ ./crc start -p ~/Downloads/pull-secret.txt
INFO Checking if running as non-root
INFO Checking if oc binary is cached
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if libvirt is enabled
INFO Checking if libvirt daemon is running
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking if libvirt ‘crc’ network is available
INFO Checking if libvirt ‘crc’ network is active
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists
INFO Extracting bundle: crc_libvirt_4.2.0-0.nightly-2019-09-26-192831.crcbundle …
ERRO Error occurred: Error getting bundle metadata: xz: data is truncated or corrupt
Logs
You can start crc with crc start --log-level debug to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.
https://gist.github.com/ajaysimha/2dcbe27465e5e1c3d137e7be7fea80c7
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 15 (8 by maintainers)
crc should be robust against that situation, we should keep this open to track it.