8000 [BUG] Mac OS installer fails to provide runnable CRC · Issue #2662 · crc-org/crc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUG] Mac OS installer fails to provide runnable CRC #2662

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.

Sign up for GitHub

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

Jump to bottom
Closed
bentito opened this issue Aug 19, 2021 · 9 comments
Closed

[BUG] Mac OS installer fails to provide runnable CRC #2662

bentito opened this issue Aug 19, 2021 · 9 comments
Labels
kind/bug Something isn't working os/macos os/windows status/stale Issue went stale; did not receive attention or no reply from the OP

Comments

@bentito
Copy link
bentito commented Aug 19, 2021 •
edited
Loading

General information

  • OS: macOS
  • Hypervisor: hyperkit
  • Did you run crc setup before starting it (Yes/No)? No
  • Running CRC on: Laptop

CRC version

CodeReady Containers version: 1.31.2+19538dab
OpenShift version: 4.8.4 (not embedded in executable)

CRC status

# Put `crc status --log-level debug` output here

CRC config

# Put `crc config view` output here

Host Operating System

ProductName:	macOS
ProductVersion:	11.5.2
BuildVersion:	20G95

Steps to reproduce

  1. Stop CRC task bar item;
  2. Run installer;
  3. Start CRC task bar item;

Expected

CRC will start.

Actual

CRC fails to start with an error like:
image

The following steps are actually needed to start as expected:

• Stop CRC task bar item;
• Run installer;
• issue crc delete from CLI;
• Start CRC task bar item;
• Start CRC from task bar
@bentito bentito added kind/bug Something isn't working status/need triage labels Aug 19, 2021
@cfergeau
Copy link
Contributor

• issue crc delete from CLI;

This should be doable from the task bar item? Or does it fail to start after upgrade?
This error message needs to be improved to be useful to the user, but what it's saying is that crc instances created with previous crc versions unfortunately cannot be used with newer crc versions. Since deleting a crc instance is a data loss operation, crc cannot do it automatically. But the tray could ask whether to do it, with an explanation. Or even better, the installer could check for this before doing the upgrade.

@bentito
Copy link
Author
bentito commented Aug 20, 2021

It’s kind of a chicken and egg scenario. The installer won’t run with the tray running. Quit tray. Run installer. Tray can’t start now due to error above. Must do delete via CLI. Perhaps the installer should just tell users to do this at the end of a successful install, for now.

@cfergeau
Copy link
Contributor

If the tray fails to start, that's a bug. I'd expect the error to only be shown when clicking "Start" in the tray menu.

@bentito
Copy link
Author
bentito commented Aug 20, 2021

Okay bug then, I'll try to document on my next go-round with the installer. But the installer makes you quit the tray to run the installer. If it's supposed to start it for you, post-install, it's not, in my environment.

@cfergeau cfergeau mentioned this issue Aug 23, 2021
Closed
8000
@bentito
Copy link
Author
bentito commented Sep 15, 2021

Here's some further documentation of the problem from the most recent 1.32.1 CRC release:
If you are running the CRC already, the CRC installer commands you to quit it (and quits itself):
image
Then you go find the installer package wherever you downloaded it, run it again, and it installs without issue. At which point you try to start a cluster using the tray, and you get:
image
By now you've learned from painful experience that the way around this is to head off to the CLI to issue: crc delete. At which point you can start a cluster from the tray without issue.

@gbraad
Copy link
Contributor
gbraad commented Oct 18, 2021

^^^ the needed delete is an inherent problem we still have with the update flow. we do not actively update the VM, but you also can't run an older version. We either indicate to the user to quit and delete?

@bentito
Copy link
Author
bentito commented Oct 18, 2021

Looks like b4567d2 covers it as a workaround, let's users know to delete.

@gbraad
Copy link
Contributor
gbraad commented Oct 19, 2021

it is not elegant, but the quickest fix we can do for now. this also affects CLI and Windows.
We will look into this

@stale
Copy link
stale bot commented Dec 19, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Dec 19, 2021
@stale stale bot closed this as completed Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Something isn't working os/macos os/windows status/stale Issue went stale; did not receive attention or no reply from the OP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gbraad @cfergeau @bentito @anjannath
0