OCPBUGS-87100: fix trailing quote in prometheus query

[dsimansk]

JIra Bug Fixes: https://redhat.atlassian.net/browse/OCPBUGS-87100

Analysis / Root cause:

Per several reports after upgrading cluster to 4.20.23 the dashboard "Control Plane" icon is never appearing green. That might be indicating an issue.

Per one of the reports there was HTTP 400 captured in the browsernetwork log

A previous change introduces a trailing " quote probably by accident.
https://github.com/openshift/console/pull/16308/changes#diff-6535e1527287e98a5b1682350eb702d6fa24be9bc798a1b18745a93853883375R15

Solution description:

Fix the " to expected '.

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

[openshift-ci-robot]

@dsimansk: This pull request references Jira Issue OCPBUGS-87100, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• 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-87100 to depend on a bug targeting a version in 4.21.0, 4.21.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:

JIra Bug Fixes: https://redhat.atlassian.net/browse/OCPBUGS-87100

Analysis / Root cause:

Per several reports after upgrading cluster to 4.20.23 the dashboard "Control Plane" icon is never appearing green. That might be indicating an issue.

Per one of the reports there was HTTP 400 captured in the browsernetwork log

A previous change introduces a trailing " quote probably by accident.

Solution description:

Fix the " to expected '.

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dsimansk
Once this PR has been reviewed and has the lgtm label, please assign jhadvig for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: e79bdf92-a591-41ce-b5e1-5b671e5969f9

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

---

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

[openshift-ci-robot]

@dsimansk: This pull request references Jira Issue OCPBUGS-87100, 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 Jira Issue OCPBUGS-87100 to depend on a bug targeting a version in 4.21.0, 4.21.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.

Details

In response to this:

JIra Bug Fixes: https://redhat.atlassian.net/browse/OCPBUGS-87100

Analysis / Root cause:

Per several reports after upgrading cluster to 4.20.23 the dashboard "Control Plane" icon is never appearing green. That might be indicating an issue.

Per one of the reports there was HTTP 400 captured in the browsernetwork log

A previous change introduces a trailing " quote probably by accident.
https://github.com/openshift/console/pull/16308/changes#diff-6535e1527287e98a5b1682350eb702d6fa24be9bc798a1b18745a93853883375R15

Solution description:

Fix the " to expected '.

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

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.

[dsimansk]

/jira refresh

[openshift-ci-robot]

@dsimansk: This pull request references Jira Issue OCPBUGS-87100, 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-87159 to target a version in 4.21.0, 4.21.z, but no target version was set

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:

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

[dsimansk]

/jira refresh

[openshift-ci-robot]

@dsimansk: This pull request references Jira Issue OCPBUGS-87100, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-87159 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-87159 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

Details

In response to this:

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

[dsimansk]

/test e2e-gcp-console

seems like infra networking issue

➤ YN0000: │ cypress@npm:14.2.1 STDOUT URL: https://download.cypress.io/desktop/14.2.1?platform=linux&arch=x64
➤ YN0000: │ cypress@npm:14.2.1 STDOUT Error: getaddrinfo EAI_AGAIN cdn.cypress.io

[dsimansk]

4.20.0-0-2026-06-04-164300-test-ci-ln-98s4mpb-latest

https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/2062570615365177344

[openshift-ci]

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