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

NO-ISSUE: [release-ocm-2.12] Bump OCP versions: 4.18, 4.16, 4.14, 4.17 #7345

Open
wants to merge 1 commit into
base: release-ocm-2.12
Choose a base branch
from

Conversation

danmanor
Copy link
Contributor

OpenShift updates: 4.17.16 -> 4.17.17, 4.18.0-rc.10 -> 4.18.1, 4.16.34-multi -> 4.16.35-multi, 4.17.16-multi -> 4.17.17-multi, 4.14.46-multi -> 4.14.48-multi, 4.14.46 -> 4.14.48, 4.18.0-rc.10-multi -> 4.18.1-multi, 4.16.34 -> 4.16.35
RHCOS updates: 4.18.0-rc.2 -> 4.18.1

/cc @rccrdpccl @gamli75

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

@danmanor: This pull request explicitly references no jira issue.

In response to this:

OpenShift updates: 4.17.16 -> 4.17.17, 4.18.0-rc.10 -> 4.18.1, 4.16.34-multi -> 4.16.35-multi, 4.17.16-multi -> 4.17.17-multi, 4.14.46-multi -> 4.14.48-multi, 4.14.46 -> 4.14.48, 4.18.0-rc.10-multi -> 4.18.1-multi, 4.16.34 -> 4.16.35
RHCOS updates: 4.18.0-rc.2 -> 4.18.1

/cc @rccrdpccl @gamli75

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 gamli75 and rccrdpccl February 25, 2025 05:12
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 25, 2025
Copy link

codecov bot commented Feb 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.33%. Comparing base (fb4cadb) to head (da233d9).

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                  @@
##           release-ocm-2.12    #7345      +/-   ##
====================================================
- Coverage             68.34%   68.33%   -0.01%     
====================================================
  Files                   257      257              
  Lines                 37644    37644              
====================================================
- Hits                  25726    25724       -2     
- Misses                 9635     9636       +1     
- Partials               2283     2284       +1     

see 1 file with indirect coverage changes

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

openshift-ci bot commented Feb 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danmanor, gamli75

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 fb4cadb and 2 for PR HEAD da233d9 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD fb4cadb and 2 for PR HEAD da233d9 in total

Copy link

openshift-ci bot commented Feb 25, 2025

@danmanor: 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/subsystem-aws da233d9 link true /test subsystem-aws
ci/prow/subsystem-kubeapi-aws da233d9 link true /test subsystem-kubeapi-aws

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.

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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants