-
Notifications
You must be signed in to change notification settings - Fork 559
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.
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
ci: add support for VM_DRIVER=podman to scripts/minikube.sh #3420
Conversation
Tests can be restarted once #3419 is merged. That PR may even re-enable the CI jobs automatically. |
4482f98
to
dfe1144
Compare
/test ci/centos/k8s-e2e-external-storage/1.22 |
dfe1144
to
ac65c7f
Compare
Pull request has been modified.
ac65c7f
to
477606c
Compare
477606c
to
cf93ba0
Compare
/retest ci/centos/mini-e2e/k8s-1.24 |
Pull request has been modified.
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <[email protected]>
The scale down/up functions fail often with "deployment not found" errors. Possibly deploying with Podman is slower than deploying in a minikube VM, and there is a delay for the deployment to become available. Signed-off-by: Niels de Vos <[email protected]>
8785652
to
41df719
Compare
In case `wget` is not installed, downloading the Helm release will fail. The `install-helm.sh` script won't return a fatal error in that case, and CI jobs continue running in an environment that is not ready. By adding a check that exist the script with a failure, the CI will now correctly report a problem when Helm can not be downloaded. See-also: ceph#3430 Signed-off-by: Niels de Vos <[email protected]>
/retest ci/centos/mini-e2e-helm/k8s-1.24 |
/retest ci/centos/k8s-e2e-external-storage/1.23 |
There are occasions where deleting a PVC (or PV) never succeeds. The reported status of the deleted object is sometimes empty, which suggests that the PVC or PV was, in fact, deleted. To diagnose the incorrect error checking, include the errors for retrying in the logs. Signed-off-by: Niels de Vos <[email protected]>
Because the rbd-nbd tests fail with minikube and the Podman driver, disable the tests for the time being. Updates: ceph#3431 Signed-off-by: Niels de Vos <[email protected]>
be6765c
to
29b0aca
Compare
e2elog.Logf("PVC %s (status: %s) has not been deleted yet, rechecking...", name, pvc.Status) | ||
|
||
return false, nil | ||
} | ||
if isRetryableAPIError(err) { | ||
e2elog.Logf("failed to verify deletion of PVC %s (status: %s): %v", name, pvc.Status, err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logging pvc name along with namespace name helps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is included in already existing logs at the start of this sub-function
if !testNBD { | ||
e2elog.Logf("skipping NBD test") | ||
|
||
return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return will skip all the tests or only this test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It returns from the current function, so it should continue with the next test. The Skip()
functions cause a more complete return, so those can not be used here.
/retest ci/centos/mini-e2e-helm/k8s-1.23 |
Failed with
|
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies.
Depends-on: #3419
Closes: #3415
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)
/retest all
: run this in case the CentOS CI failed to start/report any testprogress or results