Bug 2045008: bump discovery burst #1034

soltysh · 2022-01-25T13:09:17Z

Manual cherry-pick of a single commit bumping discovery burst from #1033

openshift-ci · 2022-01-25T13:09:22Z

@soltysh: This pull request references Bugzilla bug 2045008, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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.

deejross · 2022-01-25T17:27:46Z

/lgtm

openshift-ci · 2022-01-25T17:28:26Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deejross, soltysh

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~~ [soltysh]

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

openshift-bot · 2022-01-25T18:55:51Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2022-01-25T23:26:51Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2022-01-26T01:00:51Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-26T01:00:54Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-01-27T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-27T01:00:53Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-01-28T01:01:01Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-28T01:01:06Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-01-29T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-29T01:01:16Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-01-30T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-30T01:00:56Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-01-31T01:00:53Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-01-31T01:00:57Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-01T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-01T01:00:53Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-02T01:00:31Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-02T01:00:42Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-03T01:00:46Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-15T01:01:09Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-16T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-16T01:01:19Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-17T01:00:44Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-17T01:00:48Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-18T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-18T01:01:16Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-19T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-19T01:00:26Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-20T01:00:58Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-20T01:01:03Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-21T01:00:59Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-21T01:01:04Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-22T01:02:04Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-22T01:02:09Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is invalid:

expected dependent Bugzilla bug 2042059 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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-bot · 2022-02-23T01:01:05Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-23T01:02:25Z

@openshift-bot: This pull request references Bugzilla bug 2045008, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.9.z) matches configured target release for branch (4.9.z)
bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2042059 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2042059 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
bug has dependents

Requesting review from QA contact:
/cc @zhouying7780

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

soltysh · 2022-03-04T14:45:33Z

/label backport-risk-assessed

soltysh · 2022-03-04T14:46:30Z

/assign @zhouying7780
for cherry-pick approval

kasturinarra · 2022-03-11T17:23:17Z

/label cherry-pick-approved

openshift-ci · 2022-03-11T19:47:13Z

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

openshift-ci · 2022-03-11T19:47:58Z

@soltysh: An error was encountered updating to the MODIFIED state for bug 2045008 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message.


code 32000: Sub-component is mandatory for the component 'oc' in the product 'OpenShift Container Platform'.

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

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

Bug 2045008: bump discovery burst

fcff56a

openshift-ci bot assigned deejross Jan 25, 2022

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jan 25, 2022

openshift-ci bot requested review from deads2k and smarterclayton January 25, 2022 13:09

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 25, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 25, 2022

openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Feb 23, 2022

openshift-ci bot requested a review from zhouying7780 February 23, 2022 01:02

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 4, 2022

openshift-ci bot assigned zhouying7780 Mar 4, 2022

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 11, 2022

openshift-merge-robot merged commit 1791fd4 into openshift:release-4.9 Mar 11, 2022

soltysh deleted the bug2045008 branch March 14, 2022 16:56

Bug 2045008: bump discovery burst #1034

Bug 2045008: bump discovery burst #1034

Conversation

soltysh commented Jan 25, 2022

openshift-ci bot commented Jan 25, 2022

deejross commented Jan 25, 2022

openshift-ci bot commented Jan 25, 2022

openshift-bot commented Jan 25, 2022

openshift-bot commented Jan 25, 2022

openshift-bot commented Jan 26, 2022

openshift-ci bot commented Jan 26, 2022

openshift-bot commented Jan 27, 2022

openshift-ci bot commented Jan 27, 2022

openshift-bot commented Jan 28, 2022

openshift-ci bot commented Jan 28, 2022

openshift-bot commented Jan 29, 2022

openshift-ci bot commented Jan 29, 2022

openshift-bot commented Jan 30, 2022

openshift-ci bot commented Jan 30, 2022

openshift-bot commented Jan 31, 2022

openshift-ci bot commented Jan 31, 2022

openshift-bot commented Feb 1, 2022

openshift-ci bot commented Feb 1, 2022

openshift-bot commented Feb 2, 2022

openshift-ci bot commented Feb 2, 2022

openshift-bot commented Feb 3, 2022

openshift-ci bot commented Feb 15, 2022

openshift-bot commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

openshift-bot commented Feb 17, 2022

openshift-ci bot commented Feb 17, 2022

openshift-bot commented Feb 18, 2022

openshift-ci bot commented Feb 18, 2022

openshift-bot commented Feb 19, 2022

openshift-ci bot commented Feb 19, 2022

openshift-bot commented Feb 20, 2022

openshift-ci bot commented Feb 20, 2022

openshift-bot commented Feb 21, 2022

openshift-ci bot commented Feb 21, 2022

openshift-bot commented Feb 22, 2022

openshift-ci bot commented Feb 22, 2022

openshift-bot commented Feb 23, 2022

openshift-ci bot commented Feb 23, 2022

soltysh commented Mar 4, 2022

soltysh commented Mar 4, 2022

kasturinarra commented Mar 11, 2022

openshift-ci bot commented Mar 11, 2022

openshift-ci bot commented Mar 11, 2022