OCPBUGS-46928, OCPBUGS-46935, OCPBUGS-47315: x/net bump to v0.34.0 [release-4.16] by perdasilva · Pull Request #939 · openshift/operator-framework-olm

perdasilva · 2025-01-20T08:29:51Z

No description provided.

openshift-ci · 2025-01-20T08:32:36Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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:

~~DOWNSTREAM_OWNERS~~ [perdasilva]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: api Upstream-commit: cbc560493dab9366e79e718ddfce2512ea81c813

Upstream-repository: operator-registry Upstream-commit: 936590e4d29adfc7c1c94eaa2a5dc84d49082614

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6c8f9c33833389f4e44ffe56e7ac1151bcf7a84d

openshift-ci-robot · 2025-01-20T11:40:38Z

@perdasilva: This pull request references Jira Issue OCPBUGS-47315, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-47315 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

This pull request references Jira Issue OCPBUGS-46928, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-46928 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

This pull request references Jira Issue OCPBUGS-46935, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-46935 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

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.

perdasilva · 2025-01-20T12:12:24Z

/jira refresh

openshift-ci-robot · 2025-01-20T12:12:32Z

@perdasilva: This pull request references Jira Issue OCPBUGS-47315, which is invalid:

expected dependent Jira Issue OCPBUGS-47316 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-46928, which is invalid:

expected dependent Jira Issue OCPBUGS-46929 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-46935, which is invalid:

expected dependent Jira Issue OCPBUGS-46936 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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 · 2025-01-20T12:38:05Z

@perdasilva: This pull request references Jira Issue OCPBUGS-46928, which is invalid:

expected dependent Jira Issue OCPBUGS-46929 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

This pull request references Jira Issue OCPBUGS-46935, which is invalid:

expected dependent Jira Issue OCPBUGS-46936 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

This pull request references Jira Issue OCPBUGS-47315, which is invalid:

expected dependent Jira Issue OCPBUGS-47316 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

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.

camilamacedo86 · 2025-01-20T12:56:26Z

/lgtm

openshift-ci · 2025-01-20T13:49:14Z

@perdasilva: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

perdasilva · 2025-01-20T15:54:52Z

/label backport-risk-assessed

perdasilva · 2025-01-20T16:56:51Z

/label backport-risk-assessed

Xia-Zhao-rh · 2025-01-21T01:28:35Z

/label cherry-pick-approved
/label qe-approved

openshift-ci-robot · 2025-01-21T01:28:45Z

@perdasilva: This pull request references Jira Issue OCPBUGS-46928, which is invalid:

expected dependent Jira Issue OCPBUGS-46929 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-46935, which is invalid:

expected dependent Jira Issue OCPBUGS-46936 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-47315, which is invalid:

expected dependent Jira Issue OCPBUGS-47316 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

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.

Xia-Zhao-rh · 2025-01-21T01:38:11Z

/jira refresh

openshift-ci-robot · 2025-01-21T01:38:18Z

@Xia-Zhao-rh: This pull request references Jira Issue OCPBUGS-46928, which is invalid:

expected dependent Jira Issue OCPBUGS-46929 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-46935, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.z)
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-46936 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-46936 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

This pull request references Jira Issue OCPBUGS-47315, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.z)
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-47316 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-47316 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

Xia-Zhao-rh · 2025-01-21T01:39:37Z

/jira refresh

openshift-ci-robot · 2025-01-21T01:39:45Z

@Xia-Zhao-rh: This pull request references Jira Issue OCPBUGS-46928, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.z)
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-46929 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-46929 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

This pull request references Jira Issue OCPBUGS-46935, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.z)
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-46936 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-46936 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

This pull request references Jira Issue OCPBUGS-47315, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.z)
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-47316 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-47316 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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 · 2025-01-21T01:43:45Z

@perdasilva: Jira Issue OCPBUGS-46928: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#939

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

Jira Issue OCPBUGS-46935: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#939

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

Jira Issue OCPBUGS-47315: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#939

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

Details

In response to this:

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 · 2025-01-21T03:14:02Z

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.16.0-202501210235.p0.g1b927a4.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-01-21T03:14:02Z

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202501210235.p0.g1b927a4.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-01-21T03:20:01Z

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.16.0-202501210235.p0.g1b927a4.assembly.stream.el9.
All builds following this will include this PR.

openshift-ci Bot requested review from anik120 and dinhxuanvu January 20, 2025 08:32

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2025

bump golang.org/x/net to 0.34.0 (openshift#387)

fbd4cea

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: api Upstream-commit: cbc560493dab9366e79e718ddfce2512ea81c813

perdasilva force-pushed the xnetbump-416 branch from 5de3561 to e842bb3 Compare January 20, 2025 09:42

camilamacedo86 and others added 2 commits January 20, 2025 11:20

Upgrade github.com/joelanford/ignore from v0.1.0 to v0.1.1 (#1527)

c5af720

Upstream-repository: operator-registry Upstream-commit: 936590e4d29adfc7c1c94eaa2a5dc84d49082614

bump golang.org/x/net to 0.34.0 (#3485)

1fcca4a

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com> Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6c8f9c33833389f4e44ffe56e7ac1151bcf7a84d

perdasilva force-pushed the xnetbump-416 branch from e842bb3 to 1fcca4a Compare January 20, 2025 10:22

perdasilva changed the title ~~x/net bump [release-4.16]~~ OCPBUGS-47315, OCPBUGS-46928, OCPBUGS-46935: x/net bump to v0.34.0 [release-4.16] Jan 20, 2025

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jan 20, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 20, 2025

perdasilva changed the title ~~OCPBUGS-47315, OCPBUGS-46928, OCPBUGS-46935: x/net bump to v0.34.0 [release-4.16]~~ OCPBUGS-46928, OCPBUGS-46935, OCPBUGS-47315: x/net bump to v0.34.0 [release-4.16] Jan 20, 2025

openshift-ci Bot assigned camilamacedo86 Jan 20, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2025

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 20, 2025

openshift-ci Bot assigned bandrade, emmajiafan, jianzhangbjz, KeenonLee, kuiwang02 and Xia-Zhao-rh Jan 20, 2025

openshift-ci Bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. qe-approved Signifies that QE has signed off on this PR labels Jan 21, 2025

openshift-ci Bot requested a review from Xia-Zhao-rh January 21, 2025 01:38

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 21, 2025

openshift-merge-bot Bot merged commit 1b927a4 into openshift:release-4.16 Jan 21, 2025

Conversation

perdasilva commented Jan 20, 2025

Uh oh!

openshift-ci Bot commented Jan 20, 2025

Uh oh!

openshift-ci-robot commented Jan 20, 2025

Uh oh!

perdasilva commented Jan 20, 2025

Uh oh!

openshift-ci-robot commented Jan 20, 2025

Uh oh!

openshift-ci-robot commented Jan 20, 2025

Uh oh!

camilamacedo86 commented Jan 20, 2025

Uh oh!

openshift-ci Bot commented Jan 20, 2025

Uh oh!

perdasilva commented Jan 20, 2025

Uh oh!

perdasilva commented Jan 20, 2025

Uh oh!

Xia-Zhao-rh commented Jan 21, 2025

Uh oh!

openshift-ci-robot commented Jan 21, 2025

Uh oh!

Xia-Zhao-rh commented Jan 21, 2025

Uh oh!

openshift-ci-robot commented Jan 21, 2025

Uh oh!

Xia-Zhao-rh commented Jan 21, 2025

Uh oh!

openshift-ci-robot commented Jan 21, 2025

Uh oh!

openshift-ci-robot commented Jan 21, 2025

Uh oh!

openshift-bot commented Jan 21, 2025

Uh oh!

openshift-bot commented Jan 21, 2025

Uh oh!

openshift-bot commented Jan 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants