Skip to content
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

[QE] e2e oci image refactor #4065

Merged
merged 2 commits into from Apr 22, 2024
Merged

[QE] e2e oci image refactor #4065

merged 2 commits into from Apr 22, 2024

Conversation

adrianriobo
Copy link
Contributor

@adrianriobo adrianriobo commented Mar 12, 2024

Fixes #4040
Fixes #3932
Depends on #4019

Copy link

openshift-ci bot commented Mar 12, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from adrianriobo. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

-e TARGET_HOST=XXXX \
-e TARGET_HOST_USERNAME=XXXX \
-e TARGET_HOST_KEY_PATH=/data/id_rsa \
-e TARGET_FOLDER=crc-e2e \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this TARGET_FOLDER override the ASSETS_FOLDER of the image? because as part of container file following is what we mention

COPY images/build-e2e/lib/${OS}/* ${ASSETS_FOLDER}/

and during the build of this container image from makefile I don't see passing a ASSETS_FOLDER so not sure how run.ps1/run.sh lands to this TARGET_FOLDER.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, TARGET_FOLDER takes effect on run time, and it makes reference to the folder path where we want to copy the required resources on the target host

The ASSETS_FOLDER is defined on build time, and it is being used by the base image quay.io/rhqp/deliverest:v0.0.5

Deliverest image has some common bash functions to ssh / scp and implement the logic:

  • Copy everything on the container ASSETS_FOLDER to the remote target TARGET_FOLDER
  • Run on the remote target the command of the container
  • Copy back the folder from the target host at TARGET_RESULTS to the container path defined by OUTPUT_FOLDER
  • Remove the TARGET_FOLDER on the target host

This logic is being used on almost every test execution done against a remote target, this is why it has been abstracted into Deliverest and now each image inheriting from it just need to define its specific workload per platform / arch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah exactly, at some point I need to move those small projects to some org

@praveenkumar
Copy link
Member

praveenkumar commented Apr 15, 2024

@adrianriobo Because of this PR looks like all the openshift CI tests are failing.

https://github.com/crc-org/crc/blob/main/images/openshift-ci/Dockerfile#L12-L13 ?

The path in the makefile was $(BUILD_DIR)/linux-amd64/e2e.test which changed to $(BUILD_DIR)/e2e.test and same for integration test so better to update this file also.

@adrianriobo adrianriobo force-pushed the fix-4040 branch 3 times, most recently from 8ba0a48 to 123302a Compare April 16, 2024 10:47
@adrianriobo
Copy link
Contributor Author

Now it should be good I refactored a bit the e2e and integration building blocks on the Makefile to accommodate the changes

@adrianriobo
Copy link
Contributor Author

Wait for my ack on test to have another look I will let you know

Copy link

openshift-ci bot commented Apr 17, 2024

@adrianriobo: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 522af10 link false /test security
ci/prow/integration-crc 522af10 link true /test integration-crc
ci/prow/e2e-crc 522af10 link true /test e2e-crc

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/test-infra repository. I understand the commands that are listed here.

@adrianriobo
Copy link
Contributor Author

@praveenkumar it is working now you can review if you want the latest changes

@praveenkumar praveenkumar merged commit c188994 into crc-org:main Apr 22, 2024
19 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[QE] Review e2e image [QE] Split win-e2e GH action by preset
4 participants