OCPBUGS-665: fix version typo in yaml #690

bn222 · 2022-08-29T15:32:24Z

No description provided.

openshift-ci · 2022-08-29T15:32:27Z

@bn222: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another 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.

openshift-ci-robot · 2022-08-29T15:32:28Z

@bn222: This pull request references Jira Issue OCPBUGS-582, which is invalid:

expected the bug to target the "4.11.z" version, but it targets "4.12" instead
expected Jira Issue OCPBUGS-582 to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

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.

bn222 · 2022-08-29T15:33:17Z

@zeeke

openshift-ci · 2022-08-29T15:33:53Z

@bn222: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another 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.

openshift-ci-robot · 2022-08-29T15:33:53Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected the bug to target the "4.11.z" version, but it targets "4.11" instead
expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

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.

bn222 · 2022-08-29T15:34:41Z

/jira refresh

openshift-ci-robot · 2022-08-29T15:34:43Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected the bug to target the "4.11.z" version, but it targets "4.11" instead
expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

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-08-30T09:37:21Z

/lgtm
/approve

openshift-ci · 2022-08-30T09:37:58Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bn222, 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,bn222]

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

bn222 · 2022-08-30T11:05:47Z

/label backport-risk-assessed

bn222 · 2022-08-30T11:06:00Z

/jira refresh

openshift-ci-robot · 2022-08-30T11:06:02Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected the bug to target the "4.11.z" version, but it targets "4.11" instead
expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

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.

bn222 · 2022-08-30T15:42:30Z

/jira refresh

openshift-ci-robot · 2022-08-30T15:42:32Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

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.

bn222 · 2022-09-21T12:34:48Z

/jira refresh

openshift-ci-robot · 2022-09-21T12:34:51Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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

bn222 · 2022-09-21T12:35:10Z

/jira refresh

openshift-ci-robot · 2022-09-21T12:35:12Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

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.

bn222 · 2022-09-22T08:53:24Z

/jira refresh

openshift-ci-robot · 2022-09-22T08:53:27Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

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.

bn222 · 2022-09-22T09:04:50Z

/jira refresh

openshift-ci-robot · 2022-09-22T09:04:52Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected Jira Issue OCPBUGS-665 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

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.

bn222 · 2022-09-22T10:09:21Z

/jira refresh

openshift-ci-robot · 2022-09-22T10:09:24Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected dependent Jira Issue OCPBUGS-1637 to target a version in 4.12.0, but it targets "4.12" 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.

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.

bn222 · 2022-09-22T10:09:46Z

/jira refresh

openshift-ci-robot · 2022-09-22T10:09:48Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected dependent Jira Issue OCPBUGS-1637 to target a version in 4.12.0, but it targets "4.12" 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.

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.

bn222 · 2022-09-22T10:10:03Z

/jira refresh

openshift-ci-robot · 2022-09-22T10:10:06Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is invalid:

expected dependent Jira Issue OCPBUGS-1637 to target a version in 4.12.0, but it targets "4.12" 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.

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.

bn222 · 2022-09-22T10:10:33Z

/jira refresh

openshift-ci-robot · 2022-09-22T10:10:37Z

@bn222: This pull request references Jira Issue OCPBUGS-665, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.11.z) matches configured target version for branch (4.11.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
dependent bug Jira Issue OCPBUGS-1637 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
dependent Jira Issue OCPBUGS-1637 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
bug has dependents

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.

bn222 · 2022-09-22T10:11:09Z

/retest

bn222 · 2022-09-22T10:11:22Z

/label cherry-pick-approved

openshift-ci · 2022-09-22T10:11:23Z

@bn222: Can not set label cherry-pick-approved: Must be member in one of these teams: []

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.

zhaozhanqi · 2022-09-22T13:29:39Z

/label cherry-pick-approved

openshift-ci · 2022-09-22T14:53:08Z

@bn222: 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-robot · 2022-09-22T15:06:43Z

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

openshift/sriov-network-operator#690

Jira Issue OCPBUGS-665 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.

zhaozhanqi · 2022-09-23T02:11:02Z

/label qe-approve

openshift-ci · 2022-09-23T02:11:04Z

@zhaozhanqi: The label(s) /label qe-approve cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved

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.

zhaozhanqi · 2022-09-23T02:11:19Z

/label qe-approved

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 29, 2022

openshift-ci bot requested review from s1061123 and zshi-redhat August 29, 2022 15:33

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

bn222 changed the title ~~OCPBUGS-582: fix version typo in yaml~~ OCPBUGS-665: fix version typo in yaml Aug 29, 2022

openshift-ci-robot removed the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 29, 2022

OCPBUGS-665: fix version typo in yaml

d25397b

bn222 force-pushed the release-4.11 branch from eeb788d to d25397b Compare August 29, 2022 15:34

openshift-ci bot assigned SchSeba Aug 30, 2022

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

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 30, 2022

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Sep 22, 2022

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 22, 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 Sep 22, 2022

openshift-merge-robot merged commit 542e926 into openshift:release-4.11 Sep 22, 2022

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Sep 23, 2022

OCPBUGS-665: fix version typo in yaml #690

OCPBUGS-665: fix version typo in yaml #690

Conversation

bn222 commented Aug 29, 2022

openshift-ci bot commented Aug 29, 2022

openshift-ci-robot commented Aug 29, 2022

bn222 commented Aug 29, 2022

openshift-ci bot commented Aug 29, 2022

openshift-ci-robot commented Aug 29, 2022

bn222 commented Aug 29, 2022

openshift-ci-robot commented Aug 29, 2022

SchSeba commented Aug 30, 2022

openshift-ci bot commented Aug 30, 2022

bn222 commented Aug 30, 2022

bn222 commented Aug 30, 2022

openshift-ci-robot commented Aug 30, 2022

bn222 commented Aug 30, 2022

openshift-ci-robot commented Aug 30, 2022

bn222 commented Sep 21, 2022

openshift-ci-robot commented Sep 21, 2022

bn222 commented Sep 21, 2022

openshift-ci-robot commented Sep 21, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

bn222 commented Sep 22, 2022

bn222 commented Sep 22, 2022

openshift-ci bot commented Sep 22, 2022

zhaozhanqi commented Sep 22, 2022

openshift-ci bot commented Sep 22, 2022

openshift-ci-robot commented Sep 22, 2022

zhaozhanqi commented Sep 23, 2022

openshift-ci bot commented Sep 23, 2022

zhaozhanqi commented Sep 23, 2022