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.

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

OCPBUGS-48309: [release-4.17] submodule update 02 19 #2731

Open
wants to merge 9 commits into
base: release-4.17
Choose a base branch
from
Open

OCPBUGS-48309: [release-4.17] submodule update 02 19 #2731

wants to merge 9 commits into from
+1,096 −492

Conversation

jrvaldes
Copy link
Contributor

This PR updates the submodules and fixes windows_exporter to 4.17 branch

Ran:

./hack/update_submodules.sh release-4.17

@jrvaldes
[submodule] set windows_exporter to 4.17 branch
15a100d
@jrvaldes
[vendor] fix golang.org/x/exp for go1.22
69295ee 
ran:
go mod tidy && go mod vendor && go mod verify
@jrvaldes
[submodule][ovn-kubernetes] Update to aa5bec3a1
a46c8ea 
Update to openshift/ovn-kubernetes@aa5bec3

This commit was generated using hack/update_submodules.sh
@jrvaldes
[submodule][kubelet] Update to 75240ebc82a
1ff84c7 
Update to openshift/kubernetes@75240eb

This commit was generated using hack/update_submodules.sh
@jrvaldes
[build] Update kubelet version to v1.30.9+75240eb
7dfcaa9 
This commit was generated using hack/update_submodules.sh
@jrvaldes
[vendor] Use v1.30.9+75240eb k8s and OpenShift libraries
c0c4b51 
This commit was generated using hack/update_submodules.sh
@jrvaldes
[submodule][containerd] Update to bcc810d6b
f924455 
Update to openshift/containerd@bcc810d

This commit was generated using hack/update_submodules.sh
@jrvaldes
[build] Update containerd version to v1.7.25
f1ee224 
This commit was generated using hack/update_submodules.sh
@jrvaldes
[submodule][csi-proxy] Update to 0939e7a
477d1b7 
Update to openshift/csi-proxy@0939e7a

This commit was generated using hack/update_submodules.sh
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 Feb 19, 2025
@openshift-ci-robot
Copy link

@jrvaldes: This pull request references Jira Issue OCPBUGS-48309, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48306 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-48306 targets the "4.18.0" version, which is one of the valid target versions: 4.18.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:

This PR updates the submodules and fixes windows_exporter to 4.17 branch

Ran:

./hack/update_submodules.sh release-4.17

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 Feb 19, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 19, 2025

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

@jrvaldes
Copy link
Contributor Author

/test ?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 19, 2025

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

/test aws-e2e-operator

/test azure-e2e-operator

/test azure-e2e-upgrade

/test build

/test ci-bundle-wmco-bundle

/test gcp-e2e-operator

/test images

/test lint

/test nutanix-e2e-operator

/test platform-none-vsphere-e2e-operator

/test security

/test unit

/test vsphere-disconnected-e2e-operator

/test vsphere-e2e-operator

/test vsphere-proxy-e2e-operator

/test wicd-unit-vsphere

Use /test all to run all jobs.

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.

@jrvaldes
Copy link
Contributor Author

/test lint

@jrvaldes
Copy link
Contributor Author

/test unit

@jrvaldes
Copy link
Contributor Author

/test build

@wgahnagl
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2025
@jrvaldes jrvaldes mentioned this pull request Feb 19, 2025
Closed
@jrvaldes jrvaldes marked this pull request as ready for review February 19, 2025 21:18
@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 Feb 19, 2025
@jrvaldes jrvaldes mentioned this pull request Feb 19, 2025
Closed
@jrvaldes
Copy link
Contributor Author

/retest-required

@jrvaldes
Copy link
Contributor Author

/retest-required

2 similar comments
@jrvaldes
Copy link
Contributor Author

/retest-required

@jrvaldes
Copy link
Contributor Author

/retest-required

@jrvaldes
Copy link
Contributor Author 

/test azure-e2e-operator

@jrvaldes
Copy link
Contributor Author

@openshift/openshift-team-windows-containers PTAL

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

to get another data point

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

timed out

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

@jrvaldes
Copy link
Contributor Author

/retest

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

@jrvaldes
Copy link
Contributor Author

/test azure-e2e-operator

ipi install failed

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Mar 3, 2025

/test azure-e2e-operator

machine creation timed out

@sebsoto
Copy link
Contributor

sebsoto commented Mar 4, 2025

/retest

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Mar 4, 2025

/test azure-e2e-operator

ipi install failed

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Mar 6, 2025

/test azure-e2e-operator

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 6, 2025

@jrvaldes: 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.

@jrvaldes
Copy link
Contributor Author

jrvaldes commented Mar 6, 2025

@mansikulkarni96 PTAL

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, mansikulkarni96

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 Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mansikulkarni96 mansikulkarni96 mansikulkarni96 approved these changes

@sebsoto sebsoto Awaiting requested review from sebsoto

Assignees

@wgahnagl wgahnagl

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@jrvaldes @openshift-ci-robot @wgahnagl @sebsoto @mansikulkarni96