console [release-4.10] Bug 2080389: Fix the machine configuration docs link

/assign spadgett

Jul 07 '22 07:07 jhadvig

@jhadvig: This pull request references Bugzilla bug 2071747, which is invalid:

expected the bug to target the "4.10.z" release, but it targets "4.11.0" instead
expected Bugzilla bug 2071747 to depend on a bug targeting a release in 4.11.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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.

Jul 07 '22 07:07 openshift-ci[bot]

@jhadvig: This pull request references Bugzilla bug 2080389, which is invalid:

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

Jul 07 '22 07:07 openshift-ci[bot]

@jhadvig: 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.

Jul 07 '22 10:07 openshift-ci[bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, spadgett

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:

~~frontend/public/components/dashboard/OWNERS~~ [jhadvig,spadgett]

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

Jul 07 '22 12:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 08 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 08 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 09 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 09 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 10 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 10 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 11 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 11 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 12 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 12 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 13 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 13 '22 01:07 openshift-ci[bot]

@jhadvig According to https://github.com/openshift/console/pull/11796, pr11795 is not needed now, if will you open the old pr11421?

Jul 13 '22 07:07 yanpzhan

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 14 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 14 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 15 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 15 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 16 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 16 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 17 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 17 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 18 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 18 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 19 '22 01:07 openshift-bot

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

expected dependent Bugzilla bug 2071747 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2071747 to target a release in 4.11.0, but it targets "4.12.0" 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.

Jul 19 '22 01:07 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Jul 20 '22 01:07 openshift-bot