[rhcos-4.16]: mantle/kola: make iscsi tests use virtiofs mounted COSA rootfs #4020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pulling COSA from quay takes a good amount of time. Let's bump this so the service doesn't timeout like has been seen: ``` Jan 27 13:27:10 localhost systemd[1]: Starting Boot VM over iSCSI... Jan 27 13:28:21 localhost chronyd[1116]: Can't synchronise: no selectable sources Jan 27 13:28:21 localhost chronyd[1116]: Source 149.28.200.179 replaced with 67.217.246.204 (2.rhel.pool.ntp.org) Jan 27 13:31:16 localhost systemd[1289]: Created slice User Background Tasks Slice. Jan 27 13:31:16 localhost systemd[1289]: Starting Cleanup of User's Temporary Files and Directories... Jan 27 13:31:16 localhost systemd[1289]: Finished Cleanup of User's Temporary Files and Directories. Jan 27 13:31:26 localhost systemd[1]: coreos-iscsi-vm.service: start operation timed out. Terminating. Jan 27 13:31:26 localhost systemd[1]: coreos-iscsi-vm.service: Main process exited, code=exited, status=1/FAILURE Jan 27 13:31:26 localhost systemd[1]: coreos-iscsi-vm.service: Failed with result 'timeout'. ```
We've seen errors in the RHCOS pipeline where the iSCSI tests are hitting the 10m timeout. We could bump the timeout, but first let's try pulling the COSA image in a separate unit so that it can happen in parallel with the install over iSCSI so that when we're ready to start the VM the image is already there.
In this case we'll run the podman container with --rootfs instead of pulling a full 4+ GiB COSA image from quay for `kola qemuexec`. This saves us quite a bit of time and bandwidth usage during a pipeline run because we have more than 1 iscsi test. This should also take care of coreos/fedora-coreos-tracker#1866 because we are no longer pulling this particular container from quay.
aaradhak
approved these changes
Feb 4, 2025
|
/retest |
|
@marmijo: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
CI is failing with: |
|
yeah. See https://pagure.io/koji/issue/4295#comment-953957 I ran that and re-triggered CI here. /retest |
|
Thanks @dustymabe! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport #4013 to
rhcos-4.16.In this case we'll run the podman container with --rootfs instead
of pulling a full 4+ GiB COSA image from quay for kola qemuexec.
This saves us quite a bit of time and bandwidth usage during a
pipeline run because we have more than 1 iscsi test.
This should also take care of coreos/fedora-coreos-tracker#1866
because we are no longer pulling this particular container from quay.