Skip to content

USHIFT-4127: Port upgrade tests to bootc #3991

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 22 commits into from
Oct 28, 2024
Merged

USHIFT-4127: Port upgrade tests to bootc #3991

merged 22 commits into from
Oct 28, 2024

Conversation

ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Sep 27, 2024 •
edited
Loading

See this JIRA comment for the list of tests ported and affected.

Note that the following tests were duplicated in presubmits and periodics of the ostree scenarios and they were deleted in the ostree periodics to avoid duplication.

@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 27, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 27, 2024 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-4127 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

To be followed by periodic tests.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 27, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 27, 2024
@ggiguash
Copy link
Contributor Author

/test ?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

@ggiguash: The following commands are available to trigger required jobs:

  • /test e2e-aws-footprint-and-performance
  • /test e2e-aws-tests
  • /test e2e-aws-tests-arm
  • /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-cache
  • /test e2e-aws-tests-cache-arm
  • /test e2e-aws-tests-periodic
  • /test e2e-aws-tests-periodic-arm
  • /test images
  • /test ocp-conformance-rhel-eus
  • /test ocp-conformance-rhel-eus-arm
  • /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 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-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-images
  • pull-ci-openshift-microshift-main-test-unit
  • pull-ci-openshift-microshift-main-verify

In response to this:

/test ?

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.

@ggiguash
Copy link
Contributor Author

/test e2e-aws-tests-bootc

1 similar comment
@ggiguash
Copy link
Contributor Author

/test e2e-aws-tests-bootc

@ggiguash
Copy link
Contributor Author

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

@ggiguash ggiguash force-pushed the bootc_upgrade_tests branch from 109872f to 331a064 Compare October 14, 2024 12:46
@ggiguash ggiguash force-pushed the bootc_upgrade_tests branch from 331a064 to b68c8e3 Compare October 14, 2024 12:51
@ggiguash
Copy link
Contributor Author

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

@ggiguash ggiguash force-pushed the bootc_upgrade_tests branch from 352f550 to 715f891 Compare October 15, 2024 20:50
@ggiguash
Copy link
Contributor Author

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

@ggiguash
Copy link
Contributor Author

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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 16, 2024 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-4127 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

To be followed by periodic tests.

See this JIRA comment for the list of tests ported and affected.

Note that the following tests were duplicated in presubmits and periodics of the ostree scenarios and they were deleted in the ostree periodics to avoid duplication.

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-robot
Copy link

openshift-ci-robot commented Oct 16, 2024 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-4127 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

To be followed by periodic tests.

See this JIRA comment for the list of tests ported and affected.

Note that the following tests were duplicated in presubmits and periodics of the ostree scenarios and they were deleted in the ostree periodics to avoid duplication.

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-robot
Copy link

openshift-ci-robot commented Oct 16, 2024 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-4127 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

To be followed by periodic tests in a separate PR.

See this JIRA comment for the list of tests ported and affected.

Note that the following tests were duplicated in presubmits and periodics of the ostree scenarios and they were deleted in the ostree periodics to avoid duplication.

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.

@ggiguash ggiguash marked this pull request as ready for review October 16, 2024 06:44
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 16, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 477b177 and 2 for PR HEAD 9541b83 in total

2 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 477b177 and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 477b177 and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96d88dd and 2 for PR HEAD 9541b83 in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96d88dd and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96d88dd and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96d88dd and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a27fa69 and 2 for PR HEAD 9541b83 in total

4 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a27fa69 and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a27fa69 and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a27fa69 and 2 for PR HEAD 9541b83 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a27fa69 and 2 for PR HEAD 9541b83 in total

@ggiguash
Copy link
Contributor Author

/retest-required

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 26, 2024
@ggiguash ggiguash marked this pull request as draft October 26, 2024 05:14
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 26, 2024
@ggiguash ggiguash force-pushed the bootc_upgrade_tests branch from 8bd3b76 to 925f610 Compare October 26, 2024 05:57
@ggiguash ggiguash marked this pull request as ready for review October 26, 2024 06:15
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 26, 2024
@ggiguash ggiguash mentioned this pull request Oct 27, 2024
Closed
@ggiguash
Copy link
Contributor Author

/retest-required

@pmtk
Copy link
Member

pmtk commented Oct 28, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 28, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described 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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 470b98d and 2 for PR HEAD c64ea7b in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 28, 2024

@ggiguash: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit b172906 into openshift:main Oct 28, 2024
12 checks passed
@ggiguash ggiguash deleted the bootc_upgrade_tests branch October 30, 2024 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dhensel-rh dhensel-rh Awaiting requested review from dhensel-rh

@vanhalenar vanhalenar Awaiting requested review from vanhalenar

@copejon copejon Awaiting requested review from copejon

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1

1 more reviewer

@pmtk pmtk pmtk left review comments

Reviewers whose approvals may not affect merge requirements
Assignees

@pmtk pmtk

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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ggiguash @openshift-ci-robot @pmtk