[release-4.18] OCPBUGS-58675,OCPBUGS-58670: bump github.com/golang/glog to v1.2.5 #556

damdo · 2025-07-11T07:14:46Z

bump github.com/golang/glog to v1.2.5

JoelSpeed · 2025-07-11T07:54:25Z

Bug link?

damdo · 2025-07-11T10:24:34Z

@JoelSpeed added

openshift-ci-robot · 2025-07-11T10:24:36Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, 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-58675 to depend on a bug targeting a version in 4.19.0, 4.19.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-58670, 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-58670 to depend on a bug targeting a version in 4.19.0, 4.19.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.

In response to this:

bump github.com/golang/glog to v1.2.5

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.

theobarberbany · 2025-07-11T10:56:42Z

/lgtm
/approve

damdo · 2025-07-11T10:58:44Z

/retest

damdo · 2025-07-11T12:08:14Z

/jira refresh

openshift-ci-robot · 2025-07-11T12:08:22Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, which is invalid:

expected dependent Jira Issue OCPBUGS-59242 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
expected dependent Jira Issue OCPBUGS-59242 to target a version in 4.19.0, 4.19.z, but no target version was set

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-58670, 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 dependent Jira Issue OCPBUGS-59241 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
expected dependent Jira Issue OCPBUGS-59241 to target a version in 4.19.0, 4.19.z, but no target version was set

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.

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.

damdo · 2025-07-11T12:11:14Z

/jira refresh

openshift-ci-robot · 2025-07-11T12:11:20Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, which is invalid:

expected dependent Jira Issue OCPBUGS-59242 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) 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-58670, which is invalid:

expected dependent Jira Issue OCPBUGS-59241 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) 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.

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.

damdo · 2025-07-11T12:12:20Z

/jira refresh

openshift-ci-robot · 2025-07-11T12:12:32Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-59242 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-59242 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

Requesting review from QA contact:
/cc @xiaojiey

This pull request references Jira Issue OCPBUGS-58670, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-59241 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-59241 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

Requesting review from QA contact:
/cc @xiaojiey

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.

JoelSpeed · 2025-07-11T12:26:20Z

In 4.19, we are using 1.2.4, is this going to cause any issues when folks upgrade?

damdo · 2025-07-11T12:32:13Z

In 4.19, we are using 1.2.4, is this going to cause any issues when folks upgrade?

Good point, I can bump it there too

damdo · 2025-07-11T12:42:33Z

Created this on main to bump it there and go then down to 4.19: #557

damdo · 2025-07-17T08:58:06Z

/assign @JoelSpeed

for approval

damdo · 2025-07-17T08:58:19Z

/label backport-risk-assessed

JoelSpeed · 2025-07-17T11:02:07Z

/approve

openshift-ci · 2025-07-17T11:02:22Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, theobarberbany

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:

~~OWNERS~~ [JoelSpeed]

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

huali9 · 2025-07-18T08:01:59Z

Based on the capi regression job passed, so add label
/label qe-approved

openshift-ci-robot · 2025-07-18T08:02:11Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, which is invalid:

expected dependent Jira Issue OCPBUGS-59242 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
expected dependent Jira Issue OCPBUGS-59243 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" 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-58670, which is invalid:

expected dependent Jira Issue OCPBUGS-59241 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
expected dependent Jira Issue OCPBUGS-59244 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" 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.

In response to this:

bump github.com/golang/glog to v1.2.5

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.

damdo · 2025-07-18T08:05:25Z

/jira refresh

openshift-ci-robot · 2025-07-18T08:05:36Z

@damdo: This pull request references Jira Issue OCPBUGS-58675, which is invalid:

expected dependent Jira Issue OCPBUGS-59242 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
expected dependent Jira Issue OCPBUGS-59243 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" 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-58670, which is invalid:

expected dependent Jira Issue OCPBUGS-59241 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
expected dependent Jira Issue OCPBUGS-59244 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" 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.

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.

huali9 · 2025-07-18T08:12:27Z

/jira refresh

openshift-ci-robot · 2025-07-18T08:12:36Z

@huali9: This pull request references Jira Issue OCPBUGS-58675, which is valid.

9 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-59242 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 bug Jira Issue OCPBUGS-59243 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-59242 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
dependent Jira Issue OCPBUGS-59243 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

Requesting review from QA contact:
/cc @huali9

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

9 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-59241 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 bug Jira Issue OCPBUGS-59244 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-59241 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
dependent Jira Issue OCPBUGS-59244 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

Requesting review from QA contact:
/cc @huali9

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.

damdo · 2025-07-18T08:28:37Z

/tide refresh

damdo · 2025-07-18T08:50:06Z

/tide refresh

damdo · 2025-07-18T12:32:36Z

/tide refresh

damdo · 2025-07-18T12:34:28Z

/override ci/prow/okd-scos-images

openshift-ci · 2025-07-18T12:34:43Z

@damdo: Overrode contexts on behalf of damdo: ci/prow/okd-scos-images

In response to this:

/override ci/prow/okd-scos-images

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.

openshift-ci · 2025-07-18T12:34:45Z

@damdo: 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-ci-robot · 2025-07-18T12:39:28Z

@damdo: Jira Issue OCPBUGS-58675: All pull requests linked via external trackers have merged:

openshift/cluster-api-provider-aws#556

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

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

openshift/cluster-api-provider-aws#556

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

In response to this:

bump github.com/golang/glog to v1.2.5

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-07-22T04:31:49Z

[ART PR BUILD NOTIFIER]

Distgit: ose-aws-cluster-api-controllers
This PR has been included in build ose-aws-cluster-api-controllers-container-v4.18.0-202507211933.p0.gd631c22.assembly.stream.el9.
All builds following this will include this PR.

UPSTREAM: <carry>: bump github.com/golang/glog to v1.2.5

9e253cc

openshift-ci bot requested review from JoelSpeed and elmiko July 11, 2025 07:15

damdo changed the title ~~[release-4.18] bump github.com/golang/glog to v1.2.5~~ [release-4.18] OCPBUGS-58675,OCPBUGS-58670: bump github.com/golang/glog to v1.2.5 Jul 11, 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 Jul 11, 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 Jul 11, 2025

openshift-ci bot assigned theobarberbany Jul 11, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 11, 2025

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

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

openshift-ci bot requested a review from xiaojiey July 11, 2025 12:12

This was referenced Jul 16, 2025

OCPBUGS-59243,OCPBUGS-59244: UPSTREAM: 5590: Bump golog v1.2.5 #557

Merged

[release-4.19] OCPBUGS-59241,OCPBUGS-59242: bump github.com/golang/glog to v1.2.5 #558

Merged

openshift-ci bot assigned JoelSpeed Jul 17, 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 Jul 17, 2025

openshift-ci bot assigned huali9, miyadav and sunzhaohua2 Jul 17, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2025

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 18, 2025

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

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 Jul 18, 2025

openshift-ci bot requested a review from huali9 July 18, 2025 08:12

openshift-merge-bot bot merged commit d631c22 into openshift:release-4.18 Jul 18, 2025
13 checks passed

[release-4.18] OCPBUGS-58675,OCPBUGS-58670: bump github.com/golang/glog to v1.2.5 #556

[release-4.18] OCPBUGS-58675,OCPBUGS-58670: bump github.com/golang/glog to v1.2.5 #556

Uh oh!

Conversation

damdo commented Jul 11, 2025

Uh oh!

JoelSpeed commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

openshift-ci-robot commented Jul 11, 2025

Uh oh!

theobarberbany commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

openshift-ci-robot commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

openshift-ci-robot commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

openshift-ci-robot commented Jul 11, 2025

Uh oh!

JoelSpeed commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

damdo commented Jul 11, 2025

Uh oh!

damdo commented Jul 17, 2025

Uh oh!

damdo commented Jul 17, 2025

Uh oh!

JoelSpeed commented Jul 17, 2025

Uh oh!

openshift-ci bot commented Jul 17, 2025

Uh oh!

huali9 commented Jul 18, 2025

Uh oh!

openshift-ci-robot commented Jul 18, 2025

Uh oh!

damdo commented Jul 18, 2025

Uh oh!

openshift-ci-robot commented Jul 18, 2025

Uh oh!

huali9 commented Jul 18, 2025

Uh oh!

openshift-ci-robot commented Jul 18, 2025

Uh oh!

damdo commented Jul 18, 2025

Uh oh!

damdo commented Jul 18, 2025

Uh oh!

damdo commented Jul 18, 2025

Uh oh!

damdo commented Jul 18, 2025

Uh oh!

openshift-ci bot commented Jul 18, 2025

Uh oh!

openshift-ci bot commented Jul 18, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 18, 2025

Uh oh!

openshift-bot commented Jul 22, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants