jsliacan

Wrong syntax when verifying version of xhyve in install instructions (Minishift on Mac OS)

13

### General information * Minishift version: v1.33.0+ba29431 * OS: macOS * Hypervisor: xhyve / VirtualBox ### Steps to reproduce 1. If virtualization environment not set up, follow instruction as given...

[Integration] Podman preset tests

7

**Relates to:** Issue #2920 This PR sets up integration tests to work with podman preset on all 3 platforms. The test itself is barely populated, but this will be remedied...

[QE] Compactify e2e tests

11

This PR contains the following changes - include the relevant clicumber code in this codebase, as suggested in #2538 and #3210 - update dependencies (cucumber/godog/...) - compactify features/scenarios to fit...

[BUG] More than ~30% of `crc start` commands end with cluster in `Starting` state

2

## CRC version ```bash CRC version: 2.2.2+f1e1d3e OpenShift version: 4.10.9 Podman version: 3.4.4 ``` It happens more and more often that the cluster is not ready after CRC start finishes....

[QE] Move config test from e2e to integration

1

Consider which parts of `config.feature` are still relevant and retain those as part of a new integration test. Add checks: - if monitoring is enabled, memory requirement is [14GiB](https://access.redhat.com/documentation/en-us/red_hat_openshift_local/2.5/html/getting_started_guide/administrative-tasks_gsg#starting-monitoring_gsg) -...

All values are default values in new fields added with fitgen

7

I'm not sure if this is an issue, but I need help figuring out why all values from `radar_current`, `radar_speeds`, etc. fields that I added with `fitgen` default to max...

[E2e] testsuite maintenance

7

**Fixes:** Issue #4018 and #3997

### General information Recently, [some](https://github.com/crc-org/crc/actions/runs/7900918014/job/21563444025) `windows-e2e` workflow runs fail with ```bash Copy resources to target ssh: connect to host 20.88.32.35 port 22: Connection refused ssh: connect to host 20.88.32.35 port...

[QE] Add debug steps and connection check step to `windows-e2e` workflow

2

**Related to:** Issue #4034

Re: Issue #3741 We have been seeing regular (not consistent) failures stemming from this issue throughout release testing. ```bash oc login -u kubeadmin -p YPkA2-hzWvD-cSRru-4yRDq https://api.crc.testing:6443', expected to succeed, exited...