redhat-developer / redhat-developer/vscode-openshift-tools
CRC Starter should compare OpenShift versions between crc status and crc version before starting vm
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
crc start fails when present vm has different openshift version. CRC starter should check if vm is present and has the same OpenShift version with crc before running crc start. It could be done by running crc status -o json and crc version -o json and comparing openshift version in vm and crc.
If they don't match request for deleting vm should be shown and crc delete -f && crc start executed to avoid start error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the CRC Starter pre-start flow in the TypeScript VS Code extension and trace how it invokes crc start. First inspect the JSON output from crc status -o json and crc version -o json; done means mismatched OpenShift versions are detected, the user is asked to delete the VM, and the documented delete-and-start sequence avoids the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100