[release-4.10] Bug 2078988: Fix field selector #50

openshift-cherrypick-robot · 2022-04-26T16:24:56Z

This is an automated cherry-pick of #49

/assign SchSeba

Signed-off-by: Sebastian Sch <sebassch@gmail.com>

openshift-ci · 2022-04-26T16:25:09Z

@openshift-cherrypick-robot: Bugzilla bug 2078954 has been cloned as Bugzilla bug 2078988. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2078988: Fix field selector

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-ci · 2022-04-26T16:25:15Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2078988, which is invalid:

expected dependent Bugzilla bug 2078954 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED 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-ci · 2022-04-26T17:19:40Z

@openshift-cherrypick-robot: 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.

SchSeba · 2022-04-27T14:41:10Z

/lgtm
/approve

openshift-ci · 2022-04-27T14:42:02Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, SchSeba

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

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-04-28T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-28T01:00:44Z

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

expected dependent Bugzilla bug 2078954 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-04-29T01:01:09Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

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

expected dependent Bugzilla bug 2078954 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-04-30T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-30T01:00:29Z

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

expected dependent Bugzilla bug 2078954 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-05-01T01:00:23Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

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

expected dependent Bugzilla bug 2078954 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-05-02T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-02T01:00:49Z

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

expected dependent Bugzilla bug 2078954 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-05-03T01:00:26Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-03T01:00:40Z

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

expected dependent Bugzilla bug 2078954 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-05-04T01:00:58Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-04T01:01:10Z

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

expected dependent Bugzilla bug 2078954 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-05-05T01:01:03Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-05T01:01:24Z

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

expected dependent Bugzilla bug 2078954 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-05-06T01:00:37Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-06T01:00:49Z

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

expected dependent Bugzilla bug 2078954 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-05-07T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-07T01:01:00Z

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

expected dependent Bugzilla bug 2078954 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-05-08T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-08T01:00:57Z

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

expected dependent Bugzilla bug 2078954 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-05-09T01:00:53Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

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

expected dependent Bugzilla bug 2078954 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-05-10T01:00:29Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-10T01:00:42Z

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

expected dependent Bugzilla bug 2078954 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-05-11T01:00:58Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-11T01:01:10Z

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

expected dependent Bugzilla bug 2078954 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-05-12T01:00:40Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-12T01:00:54Z

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

expected dependent Bugzilla bug 2078954 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-05-13T01:01:21Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-05-13T01:01:57Z

@openshift-bot: This pull request references Bugzilla bug 2078988, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

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

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

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-ci · 2022-05-13T01:09:12Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/network-metrics-daemon#50

Bugzilla bug 2078988 has been moved to the MODIFIED state.

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.

SchSeba · 2022-05-17T08:15:34Z

/cherry-pick release-4.9

openshift-cherrypick-robot · 2022-05-17T08:16:11Z

@SchSeba: new pull request created: #51

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.

Fix field selector

4223670

Signed-off-by: Sebastian Sch <sebassch@gmail.com>

openshift-ci bot assigned SchSeba Apr 26, 2022

openshift-cherrypick-robot mentioned this pull request Apr 26, 2022

Bug 2078954: Fix field selector #49

Merged

openshift-ci bot changed the title ~~[release-4.10] Bug 2078954: Fix field selector~~ [release-4.10] Bug 2078988: Fix field selector Apr 26, 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 Apr 26, 2022

openshift-ci bot requested review from mmirecki and SchSeba April 26, 2022 16:25

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

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 27, 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 May 13, 2022

openshift-ci bot merged commit 45712fe into openshift:release-4.10 May 13, 2022

openshift-cherrypick-robot mentioned this pull request May 17, 2022

[release-4.9] Bug 2087049: Fix field selector #51

Merged

[release-4.10] Bug 2078988: Fix field selector #50

[release-4.10] Bug 2078988: Fix field selector #50

Conversation

openshift-cherrypick-robot commented Apr 26, 2022

openshift-ci bot commented Apr 26, 2022

openshift-ci bot commented Apr 26, 2022

openshift-ci bot commented Apr 26, 2022

SchSeba commented Apr 27, 2022

openshift-ci bot commented Apr 27, 2022

openshift-bot commented Apr 28, 2022

openshift-ci bot commented Apr 28, 2022

openshift-bot commented Apr 29, 2022

openshift-ci bot commented Apr 29, 2022

openshift-bot commented Apr 30, 2022

openshift-ci bot commented Apr 30, 2022

openshift-bot commented May 1, 2022

openshift-ci bot commented May 1, 2022

openshift-bot commented May 2, 2022

openshift-ci bot commented May 2, 2022

openshift-bot commented May 3, 2022

openshift-ci bot commented May 3, 2022

openshift-bot commented May 4, 2022

openshift-ci bot commented May 4, 2022

openshift-bot commented May 5, 2022

openshift-ci bot commented May 5, 2022

openshift-bot commented May 6, 2022

openshift-ci bot commented May 6, 2022

openshift-bot commented May 7, 2022

openshift-ci bot commented May 7, 2022

openshift-bot commented May 8, 2022

openshift-ci bot commented May 8, 2022

openshift-bot commented May 9, 2022

openshift-ci bot commented May 9, 2022

openshift-bot commented May 10, 2022

openshift-ci bot commented May 10, 2022

openshift-bot commented May 11, 2022

openshift-ci bot commented May 11, 2022

openshift-bot commented May 12, 2022

openshift-ci bot commented May 12, 2022

openshift-bot commented May 13, 2022

openshift-ci bot commented May 13, 2022

openshift-ci bot commented May 13, 2022

SchSeba commented May 17, 2022

openshift-cherrypick-robot commented May 17, 2022