Skip to content

[release-4.17] OCPBUGS-77862: update go mod dependency for konflux#1114

Open
fgallott wants to merge 1 commit intoopenshift:release-4.17from
fgallott:hermetic-4.17
Open

[release-4.17] OCPBUGS-77862: update go mod dependency for konflux#1114
fgallott wants to merge 1 commit intoopenshift:release-4.17from
fgallott:hermetic-4.17

Conversation

@fgallott
Copy link

cherrypick of 4ecdd01, same as #1113

@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 24, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

cherrypick of 4ecdd01, same as #1113

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 jhadvig and spadgett February 24, 2026 09:22
@fgallott fgallott changed the title NO-JIRA: update go mod dependency for konflux [release-4.17] NO-JIRA: update go mod dependency for konflux Feb 26, 2026
@fgallott
Copy link
Author

fgallott commented Mar 2, 2026

/retest

@fgallott
Copy link
Author

fgallott commented Mar 5, 2026

/jira cherrypick OCPBUGS-77861

@openshift-ci-robot
Copy link
Contributor

@fgallott: Jira Issue OCPBUGS-77861 has been cloned as Jira Issue OCPBUGS-77862. Will retitle bug to link to clone.
/retitle OCPBUGS-77862: [release-4.17] NO-JIRA: update go mod dependency for konflux

Details

In response to this:

/jira cherrypick OCPBUGS-77861

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 changed the title [release-4.17] NO-JIRA: update go mod dependency for konflux OCPBUGS-77862: [release-4.17] NO-JIRA: update go mod dependency for konflux Mar 5, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 5, 2026
@openshift-ci-robot
Copy link
Contributor

@fgallott: This pull request references Jira Issue OCPBUGS-77862, which is invalid:

  • expected dependent Jira Issue OCPBUGS-77861 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.

Details

In response to this:

cherrypick of 4ecdd01, same as #1113

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.

@fgallott fgallott changed the title OCPBUGS-77862: [release-4.17] NO-JIRA: update go mod dependency for konflux [release-4.17] OCPBUGS-77862: update go mod dependency for konflux Mar 5, 2026
Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/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 Mar 11, 2026
@jhadvig
Copy link
Member

jhadvig commented Mar 11, 2026

/retest

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 11, 2026
@fgallott
Copy link
Author

/retest

@fgallott
Copy link
Author

/retest-required

@jhadvig
Copy link
Member

jhadvig commented Mar 16, 2026

Found 27 events for Pod e2e-aws-console-test:
* 2026-03-12T12:09:48Z 1x multiarch-tuning-operator: Set the architecture preferences in the nodeAffinity
* 2026-03-12T12:09:48Z 1x multiarch-tuning-operator: Successfully gated with the multiarch.openshift.io/scheduling-gate scheduling gate
* 2026-03-12T12:09:51Z 1x multiarch-tuning-operator: Set the supported architectures to {amd64}
* 2026-03-12T12:09:51Z 1x multiarch-tuning-operator: Successfully removed the multiarch.openshift.io/scheduling-gate scheduling gate
* 0001-01-01T00:00:00Z 0x : Successfully assigned ci-op-9vrsmbtn/e2e-aws-console-test to ip-10-29-6-68.ec2.internal
* 2026-03-12T12:09:52Z 1x multus: Add eth0 [172.24.71.88/23] from ovn-kubernetes
* 2026-03-12T12:09:52Z 1x kubelet: Pulling image "registry.access.redhat.com/ubi8"
* 2026-03-12T12:09:52Z 1x kubelet: Successfully pulled image "registry.access.redhat.com/ubi8" in 324ms (324ms including waiting). Image size: 205367773 bytes.
* 2026-03-12T12:09:52Z 1x kubelet: Created container: ci-scheduling-dns-wait
* 2026-03-12T12:09:52Z 1x kubelet: Started container ci-scheduling-dns-wait
* 2026-03-12T12:09:54Z 1x kubelet: Container image "us-docker.pkg.dev/k8s-infra-prow/images/entrypoint:v20260310-6097a43c8" already present on machine
* 2026-03-12T12:09:54Z 1x kubelet: Created container: place-entrypoint
* 2026-03-12T12:09:54Z 1x kubelet: Started container place-entrypoint
* 2026-03-12T12:09:55Z 1x kubelet: Container image "quay-proxy.ci.openshift.org/openshift/ci:ci_entrypoint-wrapper_latest" already present on machine
* 2026-03-12T12:09:55Z 1x kubelet: Created container: cp-entrypoint-wrapper
* 2026-03-12T12:09:55Z 1x kubelet: Started container cp-entrypoint-wrapper
* 2026-03-12T12:09:56Z 1x kubelet: Container image "quay-proxy.ci.openshift.org/openshift/ci@sha256:59388b309a782ef04a03761d063d3fea33a609291ae0a28432e0c0f2e74cb64e" already present on machine
* 2026-03-12T12:09:56Z 1x kubelet: Created container: inject-cli
* 2026-03-12T12:09:56Z 1x kubelet: Started container inject-cli
* 2026-03-12T12:09:57Z 1x kubelet: Pulling image "quay-proxy.ci.openshift.org/openshift/ci@sha256:bb5d331c9f7a3cb86ed3fa762d70072f6bea62d509f686531cdb51fa18cd1b47"
* 2026-03-12T12:10:13Z 1x kubelet: Successfully pulled image "quay-proxy.ci.openshift.org/openshift/ci@sha256:bb5d331c9f7a3cb86ed3fa762d70072f6bea62d509f686531cdb51fa18cd1b47" in 15.36s (15.36s including waiting). Image size: 2214927016 bytes.
* 2026-03-12T12:10:13Z 1x kubelet: Created container: test
* 2026-03-12T12:10:13Z 1x kubelet: Started container test
* 2026-03-12T12:10:13Z 1x kubelet: Container image "us-docker.pkg.dev/k8s-infra-prow/images/sidecar:v20260310-6097a43c8" already present on machine
* 2026-03-12T12:10:13Z 1x kubelet: Created container: sidecar
* 2026-03-12T12:10:13Z 1x kubelet: Started container sidecar
* 2026-03-12T12:20:45Z 1x node-controller: Node is not ready 
�[33mWARN�[0m[2026-03-12T12:36:43Z] Pod e2e-aws-console-test is being unexpectedly deleted:

/retest
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott, jhadvig

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:

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@fgallott: The following test 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-console d91d7b0 link true /test e2e-aws-console

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.

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

7 participants