Skip to content

USHIFT-6071: Add RF Test Suites: optional, osconfig and tuned into release scenarios#5386

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
agullon:USHIFT-6071
Sep 5, 2025
Merged

USHIFT-6071: Add RF Test Suites: optional, osconfig and tuned into release scenarios#5386
openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
agullon:USHIFT-6071

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Sep 1, 2025

  • add GDP config to all containerfile files for GDP RF tests
  • add missing systemd-resolved RPM package into rpm-ostree toml files
  • add new test/image-blueprints/layer2-presubmit/group1/rhel96-lrel-optionals-tuned.toml rpm-ostree ref for tuned RF tests
  • add new bootc scenarios:optional and osconfig
  • add new rpm-ostree scenarios: low-latency, optional and osconfig

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 1, 2025

@agullon: This pull request references USHIFT-6072 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 1, 2025
@agullon agullon changed the title USHIFT-6072: Add releases scenario for ISO and RPM deployment methods USHIFT-6071: Add RF Test Suites: optional, telemetry, osconfig and tunned into release scenarios Sep 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 1, 2025

@agullon: This pull request references USHIFT-6071 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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 openshift-eng/jira-lifecycle-plugin repository.

@agullon
Copy link
Contributor Author

agullon commented Sep 2, 2025

/retest-required

3 similar comments
@agullon
Copy link
Contributor Author

agullon commented Sep 2, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Sep 2, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Sep 3, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Sep 3, 2025

/test e2e-aws-tests-cache

@agullon
Copy link
Contributor Author

agullon commented Sep 3, 2025

/test e2e-aws-tests-arm-bootc-release

source "${SCRIPTDIR}/common.sh"

AWS_BUCKET_NAME="${AWS_BUCKET_NAME:-microshift-build-cache}"
AWS_BUCKET_NAME="microshift-ushift-6071-cache-us-west-2"
Copy link
Contributor Author

@agullon agullon Sep 3, 2025

Choose a reason for hiding this comment

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

this line change will be removed before merging this PR, add it to speed up this PR testing changes

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2025

@agullon: This pull request references USHIFT-6071 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

  • add GDP config to all containerfile files for GDP RF tests
  • add missing systemd-resolved RPM package into rpm-ostree toml files
  • add new test/image-blueprints/layer2-presubmit/group1/rhel96-lrel-optionals-tuned.toml rpm-ostree ref for tuned RF tests
  • add new bootc scenarios:optional and osconfig
  • add new rpm-ostree scenarios: low-latency, optional and osconfig

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 openshift-eng/jira-lifecycle-plugin repository.

@agullon agullon changed the title USHIFT-6071: Add RF Test Suites: optional, telemetry, osconfig and tunned into release scenarios USHIFT-6071: Add RF Test Suites: optional, osconfig and tuned into release scenarios Sep 3, 2025
KERNEL_VER_ARCH="${KERNEL_VER}.$(uname -m)"; \
dnf install -y git make "kernel-devel-${KERNEL_VER}" python3-pyserial && \
dnf clean all && \
git clone https://github.com/pmtk/serialsim.git /tmp/serialsim && \
Copy link
Contributor

Choose a reason for hiding this comment

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

We should not pull sources from a private repo - is there a public one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think so, I was surprised by this, though. But I think Patryk did it this way because some custom changes are needed in serialism repo. This is the PR where Patryk add it for the first time.

@agullon
Copy link
Contributor Author

agullon commented Sep 3, 2025

/retest-required

@agullon
Copy link
Contributor Author

agullon commented Sep 4, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Sep 4, 2025

/test e2e-aws-tests-bootc-periodic

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 5, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 5, 2025
@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/retest e2e-aws-tests-cache e2e-aws-tests-cache-arm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

@agullon: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving
/test e2e-aws-footprint-and-performance
/test e2e-aws-tests
/test e2e-aws-tests-arm
/test e2e-aws-tests-arm-bootc-release
/test e2e-aws-tests-arm-release
/test e2e-aws-tests-bootc
/test e2e-aws-tests-bootc-arm
/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm
/test e2e-aws-tests-bootc-release
/test e2e-aws-tests-cache
/test e2e-aws-tests-cache-arm
/test e2e-aws-tests-periodic
/test e2e-aws-tests-periodic-arm
/test e2e-aws-tests-release
/test ocp-full-conformance-rhel-eus
/test ocp-full-conformance-serial-rhel-eus
/test test-rpm
/test test-unit
/test verify

The following commands are available to trigger optional jobs:

/test images
/test security
/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-main-e2e-aws-tests
pull-ci-openshift-microshift-main-e2e-aws-tests-arm
pull-ci-openshift-microshift-main-e2e-aws-tests-arm-bootc-release
pull-ci-openshift-microshift-main-e2e-aws-tests-arm-release
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic-arm
pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release
pull-ci-openshift-microshift-main-e2e-aws-tests-periodic
pull-ci-openshift-microshift-main-e2e-aws-tests-periodic-arm
pull-ci-openshift-microshift-main-e2e-aws-tests-release
pull-ci-openshift-microshift-main-images
pull-ci-openshift-microshift-main-security
pull-ci-openshift-microshift-main-test-unit
pull-ci-openshift-microshift-main-verify
Details

In response to this:

/retest e2e-aws-tests-cache e2e-aws-tests-cache-arm

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.

@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/test e2e-aws-tests-cache e2e-aws-tests-cache-arm

@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/retest

1 similar comment
@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/retest


Router Verify Access Logging Configuration Container
[Documentation] Test ingress access logging configuration.
[Tags] ushift-6085
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

To skip only this router RF test in releases scenarios. The reason we need to skip it is that @pacevedom added this change yesterday. This change consist on a change in microshift code and in the RF tests. The current version under test in lrel is 4.20.0-ec-6, so this change is not included in the code, but it's in the RF tests. So we need temporarily skip this test until new lrel version (EC or RC) includes this change.

I created a task to myself to not forget to re-enable this test: https://issues.redhat.com/browse/USHIFT-6085

@@ -1,5 +1,7 @@
#!/bin/bash

export TEST_EXCLUDES="ushift-6085"
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need this?

@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/retest

@ggiguash
Copy link
Contributor

ggiguash commented Sep 5, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 5, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

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

The pull request process is described here

Details 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

@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/verified by release-ci jobs

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 5, 2025
@openshift-ci-robot
Copy link

@agullon: This PR has been marked as verified by release-ci jobs.

Details

In response to this:

/verified by release-ci jobs

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 openshift-eng/jira-lifecycle-plugin repository.

@agullon
Copy link
Contributor Author

agullon commented Sep 5, 2025

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 359a6bc into openshift:main Sep 5, 2025
19 checks passed
@agullon
Copy link
Contributor Author

agullon commented Sep 22, 2025

/cherrypick release-4.20

@openshift-cherrypick-robot

@agullon: #5386 failed to apply on top of branch "release-4.20":

Applying: add new releases scenario: optional, osconfig and tuned
error: mode change for test/scenarios-bootc/periodics/el96-crel@optional-sigstore.sh, which is not in current HEAD
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 add new releases scenario: optional, osconfig and tuned

Details

In response to this:

/cherrypick release-4.20

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.

agullon added a commit to agullon/microshift that referenced this pull request Sep 22, 2025
agullon pushed a commit to agullon/microshift that referenced this pull request Oct 2, 2025
USHIFT-6071: Add RF Test Suites: optional, osconfig and tuned into release scenarios
(cherry picked from commit 359a6bc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants