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.

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

OCPBUGS-42087: storage/cacher/ready: dynamically calculate the retryAfterSeconds #2225

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

bertinatto
Copy link
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 28, 2025
@openshift-ci-robot
Copy link

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

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

Requesting review from QA contact:
/cc @gangwgr

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

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-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Feb 28, 2025
Copy link

openshift-ci bot commented Feb 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto

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 Feb 28, 2025
…ryAfterSeconds

retryAfterSeconds is based on the time elapsed since the state (ready, unready) was last changed.
@bertinatto bertinatto force-pushed the backport-cacher-resilient-init-back-off branch from 7f51183 to 5dc7dcb Compare February 28, 2025 16:22
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@bertinatto bertinatto changed the title OCPBUGS-44693: storage/cacher/ready: dynamically calculate the retryAfterSeconds OCPBUGS-42087: storage/cacher/ready: dynamically calculate the retryAfterSeconds Feb 28, 2025
@openshift-ci-robot openshift-ci-robot removed the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 28, 2025
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-42087, which is invalid:

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.z" 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.

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-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 Feb 28, 2025
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Feb 28, 2025

@bertinatto: 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/unit 5dc7dcb link true /test unit
ci/prow/verify-commits 5dc7dcb link true /test verify-commits
ci/prow/verify 5dc7dcb link true /test verify

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.

@bertinatto
Copy link
Member Author

Check if this patch improves the signal from [sig-arch][Late] operators should not create watch channels very often test:

/payload-aggregate periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node 10

Copy link

openshift-ci bot commented Feb 28, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/92dd9600-f61b-11ef-87c3-a6c13f832ae5-0

@bertinatto
Copy link
Member Author

/payload 4.19 nightly blocking
/payload 4.19 nightly informing

Copy link

openshift-ci bot commented Mar 2, 2025

@bertinatto: trigger 12 job(s) of type blocking for the nightly release of OCP 4.19

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-driver-toolkit
  • periodic-ci-openshift-release-master-nightly-4.19-fips-payload-scan
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/916ba040-f7ac-11ef-9a4a-74b651ba4297-0

trigger 65 job(s) of type informing for the nightly release of OCP 4.19

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-compact-fips
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-single-node-ipv6
  • periodic-ci-openshift-release-master-nightly-4.19-console-aws
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.19-periodics-e2e-aws
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-csi
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-cgroupsv2
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-fips
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-csi
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-techpreview
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-upgrade-from-stable-4.18-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade-out-of-change
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-upi
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.19-periodics-e2e-azure
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-azure-csi
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade-out-of-change
  • periodic-ci-openshift-release-master-cnv-nightly-4.19-deploy-azure-kubevirt-ovn
  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.19-periodics-e2e-gcp
  • periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-gcp-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-gcp-ovn-rt
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-gcp-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm-upgrade
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-dualstack-techpreview
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6-techpreview
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-techpreview
  • periodic-ci-openshift-release-master-nightly-4.19-upgrade-from-stable-4.18-e2e-metal-ipi-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-dualstack
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.19-upgrade-from-stable-4.18-e2e-metal-ipi-upgrade-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ovn-assisted
  • periodic-ci-openshift-release-master-nightly-4.19-metal-ovn-single-node-recert-cluster-rename
  • periodic-ci-openshift-osde2e-main-nightly-4.19-osd-aws
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-osd-ccs-gcp
  • periodic-ci-openshift-osde2e-main-nightly-4.19-osd-gcp
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-proxy
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ovn-single-node-live-iso
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-telco5g
  • periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-csi
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-vsphere-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-vsphere-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-upi
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-upi-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-static-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/916ba040-f7ac-11ef-9a4a-74b651ba4297-1

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. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants