console
console copied to clipboard
[release-4.8] Bug 2022346: Fix clusterNetwork only selection issue with OCS
This is an automated cherry-pick of #9703
/assign bipuladh
@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug 1989440 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 53: Bugzilla_api_key is not a valid parameter for the Bugzilla::Bug::create function.
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh
.
In response to this:
[release-4.8] Bug 1989440: Fix clusterNetwork only selection issue with OCS
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cloudbehl, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/ceph-storage-plugin/OWNERS~~ [cloudbehl]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/bugzilla refresh
@sdodson: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is RELEASE_PENDING instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 1989440, which is invalid:
- expected the bug to be open, but it isn't
- expected the bug to target the "4.8.z" release, but it targets "4.9.0" instead
- expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (ERRATA) instead
- expected Bugzilla bug 1989440 to depend on a bug targeting a release in 4.9.0, 4.9.z 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:
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.