Bug 1994643: UPSTREAM: <carry>: send Retry-After when not ready with a caller opt in

[tkashem]

No description provided.

[openshift-ci-robot]

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

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

• f2219f9|UPSTREAM: : send Retry-After when not ready with a caller opt in: does not specify an upstream backport in the commit message

[openshift-ci]

@tkashem: This pull request references Bugzilla bug 1994643, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead

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

In response to this:

Bug 1994643: UPSTREAM: : send Retry-After when not ready with a caller opt in

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/test-infra repository.

[openshift-ci-robot]

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

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

• 8ae775b|UPSTREAM: : send Retry-After when not ready with a caller opt in: does not specify an upstream backport in the commit message

[openshift-ci-robot]

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

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

• 382cb50|UPSTREAM: : send Retry-After when not ready with a caller opt in: does not specify an upstream backport in the commit message

[tkashem]

/retest

[tkashem]

/retest

[sttts]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts, tkashem

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:

• DOWNSTREAM_OWNERS [sttts]

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

[sttts]

/bugzilla refresh

[openshift-ci]

@sttts: This pull request references Bugzilla bug 1994643, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.9.0) matches configured target release for branch (4.9.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gangwgr

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

[sttts]

/retest

[openshift-ci]

@tkashem: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-agnostic-cmd	382cb50	link	/test e2e-agnostic-cmd

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci]

@tkashem: All pull requests linked via external trackers have merged:

• openshift/cluster-kube-apiserver-operator#1207
• openshift/cluster-kube-apiserver-operator#1211
• openshift/kubernetes#887
• openshift/kubernetes#889
• openshift/kubernetes#906

Bugzilla bug 1994643 has been moved to the MODIFIED state.

In response to this:

Bug 1994643: UPSTREAM: : send Retry-After when not ready with a caller opt in

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/test-infra repository.