OCPBUGS-21610: revert #2166 #2172
Conversation
This reverts commit 0ee8922. as it's creating issues with the monitoring UI. Signed-off-by: Daniel Mellado <dmellado@redhat.com>
openshift-ci-robot
added
jira/severity-important
|
@danielmellado: This pull request references Jira Issue OCPBUGS-21610, which is invalid:
Comment 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielmellado, simonpasquier 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:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
danielmellado
changed the title
openshift-ci-robot
removed
jira/severity-important
|
@danielmellado: No Jira issue is referenced in the title of this pull 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. |
Could I know more? |
|
I found the slack thread, we'll need some tests if we decide to put it back :) |
|
/jira refresh |
|
@simonpasquier: No Jira issue is referenced in the title of this pull 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. |
|
/retitle OCPBUGS-21610: revert #2166 |
openshift-ci
bot
changed the title
openshift-ci-robot
added
jira/severity-important
|
@danielmellado: This pull request references Jira Issue OCPBUGS-21610, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
@danielmellado: 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. |
|
@danielmellado: Jira Issue OCPBUGS-21610: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-21610 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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-monitoring-operator-container-v4.15.0-202312010209.p0.g7dc0037.assembly.stream for distgit cluster-monitoring-operator. |
|
Fix included in accepted release 4.15.0-0.nightly-2023-12-08-202155 |
This reverts commit 0ee8922.
as it's creating issues with the monitoring UI.
------------------------ >8 ------------------------
Revert "OCPBUGS-21610: Change config to allow ipv6/4"
This reverts commit 0ee8922.
as it's creating issues with the monitoring UI.
Signed-off-by: Daniel Mellado dmellado@redhat.com