Skip to content

Comments

WIP: OCPBUGS-65896: Update library-go to remove Progressing on scaling#843

Open
tchap wants to merge 2 commits intoopenshift:masterfrom
tchap:no-progression-on-cluster-scaleup
Open

WIP: OCPBUGS-65896: Update library-go to remove Progressing on scaling#843
tchap wants to merge 2 commits intoopenshift:masterfrom
tchap:no-progression-on-cluster-scaleup

Conversation

@tchap
Copy link

@tchap tchap commented Feb 18, 2026

This is currently only open to test openshift/library-go#2128

/hold

@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 18, 2026
@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Feb 18, 2026
@openshift-ci-robot
Copy link
Contributor

@tchap: This pull request references Jira Issue OCPBUGS-65896, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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

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

Details

In response to this:

This currently tests openshift/library-go#2128

/hold

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 openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 18, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 18, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Excluded labels (none allowed) (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from ibihim and liouk February 18, 2026 22:58
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tchap
Once this PR has been reviewed and has the lgtm label, please assign liouk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@tchap
Copy link
Author

tchap commented Feb 19, 2026

/retest

This only makes the latest library-go update compatible with the current
behaviour. library-go now uses deployment controller deadline exceeded
to check for progress timeout, not a hardcoded value, which was set to
15 minutes in the past, hence 900 seconds.
@tchap tchap force-pushed the no-progression-on-cluster-scaleup branch from 0fb4392 to c8b8deb Compare February 19, 2026 08:45
@tchap
Copy link
Author

tchap commented Feb 19, 2026

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

@tchap: 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/e2e-aws-operator-encryption-perf-serial-ote-1of2 c8b8deb link false /test e2e-aws-operator-encryption-perf-serial-ote-1of2
ci/prow/e2e-aws-operator-encryption-kms-serial-ote-1of2 c8b8deb link false /test e2e-aws-operator-encryption-kms-serial-ote-1of2
ci/prow/e2e-aws-operator-encryption-serial-ote-2of2 c8b8deb link false /test e2e-aws-operator-encryption-serial-ote-2of2
ci/prow/e2e-aws-operator-parallel-ote c8b8deb link false /test e2e-aws-operator-parallel-ote
ci/prow/test-operator-integration c8b8deb link true /test test-operator-integration
ci/prow/e2e-aws-operator-encryption-rotation-serial-ote-2of2 c8b8deb link false /test e2e-aws-operator-encryption-rotation-serial-ote-2of2
ci/prow/e2e-aws-operator-encryption-serial-ote-1of2 c8b8deb link false /test e2e-aws-operator-encryption-serial-ote-1of2
ci/prow/e2e-aws-operator-encryption-rotation-serial-ote-1of2 c8b8deb link false /test e2e-aws-operator-encryption-rotation-serial-ote-1of2
ci/prow/e2e-aws-operator-serial-ote c8b8deb link false /test e2e-aws-operator-serial-ote
ci/prow/e2e-aws-operator-encryption-kms-serial-ote-2of2 c8b8deb link false /test e2e-aws-operator-encryption-kms-serial-ote-2of2
ci/prow/e2e-aws-operator-encryption-perf-serial-ote-2of2 c8b8deb link false /test e2e-aws-operator-encryption-perf-serial-ote-2of2

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

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants