OCPBUGS-83496:[release-4.19] feat: re enable dev console views by jgbernalp · Pull Request #858 · openshift/monitoring-plugin

jgbernalp · 2026-03-19T10:56:51Z

Manual backport of #831

Related change from the console side:

[release-4.19] OCPBUGS-83496: remove dev to admin links as dev monitoring views are enabled console#16174

Signed-off-by: Gabriel Bernal <gbernal@redhat.com>

openshift-ci-robot · 2026-03-19T10:56:59Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-77113, which is invalid:

expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.22" instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-77113 to depend on a bug targeting a version in 4.20.0, 4.20.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-03-19T10:57:01Z

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ce702cf7-427a-4898-8da2-25ec3d92204e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

PeterYurkovich · 2026-03-23T11:44:27Z

/lgtm

openshift-ci-robot · 2026-04-15T08:00:56Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.21.z" instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-83495 to target a version in 4.20.0, 4.20.z, but it targets "4.21.z" 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.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

jgbernalp · 2026-04-15T09:17:39Z

/jira refresh

openshift-ci-robot · 2026-04-15T09:17:45Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-83495 to target a version in 4.20.0, 4.20.z, but it targets "4.21.z" 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

jgbernalp · 2026-04-15T09:18:18Z

/jira refresh

openshift-ci-robot · 2026-04-15T09:18:23Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-83495 to target a version in 4.20.0, 4.20.z, but it targets "4.21.z" 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

jgbernalp · 2026-04-15T09:20:37Z

/jira refresh

openshift-ci-robot · 2026-04-15T09:20:42Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-83495 to target a version in 4.20.0, 4.20.z, but it targets "4.20" 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

jgbernalp · 2026-04-15T09:21:32Z

/jira refresh

openshift-ci-robot · 2026-04-15T09:21:37Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

PeterYurkovich · 2026-04-22T13:06:33Z

/lgtm

openshift-ci · 2026-04-22T13:07:43Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [PeterYurkovich,jgbernalp]

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

etmurasaki · 2026-04-22T14:40:30Z

/label qe-approved

openshift-ci-robot · 2026-04-22T14:40:43Z

@jgbernalp: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2026-04-22T15:40:10Z

@jgbernalp: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

etmurasaki · 2026-04-22T16:26:11Z

/jira refresh

openshift-ci-robot · 2026-04-22T16:26:16Z

@etmurasaki: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected dependent Jira Issue OCPBUGS-83495 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

etmurasaki · 2026-04-22T16:26:44Z

/verified by @etmurasaki

openshift-ci-robot · 2026-04-22T16:26:56Z

@etmurasaki: This PR has been marked as verified by @etmurasaki.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

etmurasaki · 2026-04-22T16:28:26Z

/jira refresh

openshift-ci-robot · 2026-04-22T16:28:31Z

@etmurasaki: This pull request references Jira Issue OCPBUGS-83496, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified 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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

etmurasaki · 2026-04-22T16:28:50Z

/jira refresh

openshift-ci-robot · 2026-04-22T16:28:57Z

@etmurasaki: This pull request references Jira Issue OCPBUGS-83496, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.19.z) matches configured target version for branch (4.19.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-83495 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-83495 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
bug has dependents

Requesting review from QA contact:
/cc @etmurasaki

Details

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 openshift-eng/jira-lifecycle-plugin repository.

etmurasaki · 2026-04-22T16:29:07Z

/verified by @etmurasaki

openshift-ci-robot · 2026-04-22T16:29:19Z

@etmurasaki: This PR has been marked as verified by @etmurasaki.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-04-22T16:32:46Z

@jgbernalp: Jira Issue OCPBUGS-83496: Some pull requests linked via external trackers have merged:

openshift/monitoring-plugin#858

The following pull request, linked via external tracker, has not merged:

openshift/console#16174 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-83496 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

jgbernalp added 3 commits March 19, 2026 11:44

feat: re enable dev console views

dc3d1a5

Signed-off-by: Gabriel Bernal <gbernal@redhat.com>

feat: unset query timeouts so they are defined in the backend

7cf344e

Signed-off-by: Gabriel Bernal <gbernal@redhat.com>

fix: make dashboards the default dev observe view

4dcb7de

Signed-off-by: Gabriel Bernal <gbernal@redhat.com>

jgbernalp requested review from PeterYurkovich, etmurasaki and zhuje March 19, 2026 10:56

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 19, 2026

jgbernalp mentioned this pull request Mar 19, 2026

[release-4.19] OCPBUGS-83496: remove dev to admin links as dev monitoring views are enabled openshift/console#16174

Open

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2026

openshift-ci Bot assigned PeterYurkovich Mar 23, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 23, 2026

jgbernalp changed the title ~~OCPBUGS-77113:[release-4.19] feat: re enable dev console views~~ OCPBUGS-83496:[release-4.19] feat: re enable dev console views Apr 15, 2026

chore: manually cherry pick 4.22 changes

2d20f13

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2026

openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Apr 22, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 22, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 22, 2026

openshift-merge-bot Bot merged commit 72885d0 into openshift:release-4.19 Apr 22, 2026
6 checks passed

Conversation

jgbernalp commented Mar 19, 2026

Uh oh!

openshift-ci-robot commented Mar 19, 2026

Uh oh!

coderabbitai Bot commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

PeterYurkovich commented Mar 23, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

jgbernalp commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

jgbernalp commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

jgbernalp commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

jgbernalp commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

PeterYurkovich commented Apr 22, 2026

Uh oh!

openshift-ci Bot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

openshift-ci Bot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

etmurasaki commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

coderabbitai Bot commented Mar 19, 2026 •

edited

Loading