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

OCPBUGS-48403: Add new images for group snapshot support #29455

Conversation

jsafrane
Copy link
Contributor

Add images required by openshift/kubernetes#2169.

How to reproduce the image list:

  1. Vendor OCPBUGS-48403: Bring groupsnapshot beta feature to 4.18 kubernetes#2169 into origin, make
  2. List images using ./openshift-tests images --upstream --to-repository=quay.io/openshift/community-e2e-images
  3. Compare with current release-4.18 openshift-tests without any PR.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 21, 2025
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-48403, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-48402 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48402 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Add images required by openshift/kubernetes#2169.

How to reproduce the image list:

  1. Vendor OCPBUGS-48403: Bring groupsnapshot beta feature to 4.18 kubernetes#2169 into origin, make
  2. List images using ./openshift-tests images --upstream --to-repository=quay.io/openshift/community-e2e-images
  3. Compare with current release-4.18 openshift-tests without any PR.

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 requested review from p0lyn0mial and sjenning January 21, 2025 09:44
@jsafrane
Copy link
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm openshift/kubernetes#2169

Copy link
Contributor

openshift-ci bot commented Jan 21, 2025

@jsafrane: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/14c69e80-d7dd-11ef-81a4-277ec891544d-0

@jsafrane jsafrane force-pushed the 4.18-add-groupsnapshot-add-images branch from df89be6 to 79b7a63 Compare January 21, 2025 11:52
@openshift-ci openshift-ci bot added the e2e-images-update Related to images used by e2e tests label Jan 21, 2025
Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented Jan 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, jsafrane

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2025
@jsafrane
Copy link
Contributor Author

/retest-required

@jsafrane
Copy link
Contributor Author

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 22, 2025
@sdodson
Copy link
Member

sdodson commented Jan 22, 2025

/label cherry-pick-approved
This is still TPNU.

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 22, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2774b2b and 2 for PR HEAD 79b7a63 in total

Copy link
Contributor

openshift-ci bot commented Jan 22, 2025

@jsafrane: 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/e2e-aws-ovn-single-node-serial 79b7a63 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 79b7a63 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 79b7a63 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade 79b7a63 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/okd-scos-e2e-aws-ovn 79b7a63 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node 79b7a63 link false /test e2e-aws-ovn-single-node

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.

@gnufied
Copy link
Member

gnufied commented Jan 22, 2025

/test e2e-metal-ipi-ovn-ipv6

@openshift-merge-bot openshift-merge-bot bot merged commit 0fd2e36 into openshift:release-4.18 Jan 23, 2025
23 of 29 checks passed
@openshift-ci-robot
Copy link

@jsafrane: Jira Issue OCPBUGS-48403: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-48403 has not been moved to the MODIFIED state.

In response to this:

Add images required by openshift/kubernetes#2169.

How to reproduce the image list:

  1. Vendor OCPBUGS-48403: Bring groupsnapshot beta feature to 4.18 kubernetes#2169 into origin, make
  2. List images using ./openshift-tests images --upstream --to-repository=quay.io/openshift/community-e2e-images
  3. Compare with current release-4.18 openshift-tests without any PR.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202501231433.p0.g0fd2e36.assembly.stream.el9.
All builds following this will include this PR.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. e2e-images-update Related to images used by e2e tests jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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
Development

Successfully merging this pull request may close these issues.