[release-4.17] OCPBUGS-78672: Namespace is not persisting when switching to developer view from the topology page of admin page by openshift-cherrypick-robot · Pull Request #16160 · openshift/console

openshift-cherrypick-robot · 2026-03-17T13:05:46Z

This is an automated cherry-pick of #14812

/assign cajieh

openshift-ci-robot · 2026-03-17T13:05:52Z

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug OCPBUGS-48491 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message.


request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle [release-4.17] : Namespace is not persisting when switching to developer view from the topology page of admin page

Details

In response to this:

This is an automated cherry-pick of #14812

/assign cajieh

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-17T13:05:54Z

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: 30c0ef86-df7c-4619-88fc-59e88c1c3bd8

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

📝 Coding Plan

Generate coding plan for human review comments

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

logonoff

/lgtm
/label backport-risk-assessed

openshift-ci · 2026-03-17T13:20:14Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, openshift-cherrypick-robot

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:

~~frontend/OWNERS~~ [logonoff]

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

cajieh · 2026-03-17T13:44:51Z

/retitle [release-4.17] OCPBUGS-78673: Namespace is not persisting when switching to developer view from the topology page of admin page

openshift-ci-robot · 2026-03-17T13:45:04Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-78673, which is invalid:

expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "4.16.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 Jira Issue OCPBUGS-78673 to depend on a bug targeting a version in 4.18.0, 4.18.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:

This is an automated cherry-pick of #14812

/assign cajieh

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.

cajieh · 2026-03-17T13:48:21Z

/retitle [release-4.17] OCPBUGS-78672: Namespace is not persisting when switching to developer view from the topology page of admin page

openshift-ci-robot · 2026-03-17T13:48:30Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-78672, 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-78672 to depend on a bug targeting a version in 4.18.0, 4.18.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:

This is an automated cherry-pick of #14812

/assign cajieh

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.

cajieh · 2026-03-17T13:56:03Z

/jira refresh

openshift-ci-robot · 2026-03-17T13:56:08Z

@cajieh: This pull request references Jira Issue OCPBUGS-78672, which is invalid:

expected Jira Issue OCPBUGS-78672 to depend on a bug targeting a version in 4.18.0, 4.18.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 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.

logonoff · 2026-03-17T14:07:36Z

/jira refresh

cajieh · 2026-03-22T11:19:43Z

/test e2e-gcp-console

cajieh · 2026-03-23T23:42:16Z

/test e2e-gcp-console

openshift-ci-robot · 2026-03-25T10:04:50Z

/retest-required

Remaining retests: 0 against base HEAD 593756f and 2 for PR HEAD a67ac8f in total

Leo6Leo · 2026-03-25T21:27:40Z

/retest-required

cajieh · 2026-03-26T08:57:44Z

/test e2e-gcp-console

Leo6Leo · 2026-03-26T23:04:10Z

/retest-required

Leo6Leo · 2026-03-27T13:39:45Z

/retest-required

cajieh · 2026-03-28T11:19:13Z

/test e2e-gcp-console

Leo6Leo · 2026-03-30T17:02:51Z

/retest-required

Leo6Leo · 2026-03-31T13:56:35Z

/retest-required

Leo6Leo · 2026-03-31T19:13:26Z

/retest-required

yapei · 2026-04-01T02:34:14Z

/retest-required

Leo6Leo · 2026-04-01T13:27:25Z

/retest-required

Leo6Leo · 2026-04-01T18:15:39Z

/retest-required

Leo6Leo · 2026-04-02T13:59:14Z

/retest-required

Leo6Leo · 2026-04-02T19:57:35Z

/retest-required

Leo6Leo · 2026-04-07T12:56:58Z

/retest-required

Leo6Leo · 2026-04-07T18:10:02Z

/retest-required

Leo6Leo · 2026-04-08T14:05:36Z

/retest-required

Leo6Leo · 2026-04-08T14:05:36Z

/retest-required

Leo6Leo · 2026-04-09T00:39:05Z

/retest-required

Leo6Leo · 2026-04-09T13:59:49Z

/retest-required

Leo6Leo · 2026-04-10T14:29:28Z

/retest-required

Leo6Leo · 2026-04-13T16:35:22Z

/retest-required

Leo6Leo · 2026-04-15T15:51:33Z

/retest-required

Leo6Leo · 2026-04-17T13:09:14Z

/retest-required

Leo6Leo · 2026-04-20T13:42:29Z

/retest-required

Leo6Leo · 2026-04-20T17:34:17Z

/retest-required

Leo6Leo · 2026-04-24T18:30:56Z

/retest-required

openshift-ci · 2026-04-24T21:35:18Z

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-console	`a67ac8f`	link	true	`/test e2e-gcp-console`

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.

Active namespace was not considered in namespace context

a67ac8f

openshift-cherrypick-robot assigned cajieh Mar 17, 2026

openshift-cherrypick-robot mentioned this pull request Mar 17, 2026

OCPBUGS-48491: Namespace is not persisting when switching to developer view from the topology page of admin page #14812

Merged

4 tasks

openshift-ci Bot changed the title ~~[release-4.17] OCPBUGS-48491: Namespace is not persisting when switching to developer view from the topology page of admin page~~ [release-4.17] : Namespace is not persisting when switching to developer view from the topology page of admin page Mar 17, 2026

openshift-ci Bot requested review from Leo6Leo and jhadvig March 17, 2026 13:06

openshift-ci Bot added the component/core Related to console core functionality label Mar 17, 2026

logonoff reviewed Mar 17, 2026

View reviewed changes

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 17, 2026

openshift-ci Bot assigned sanketpathak, XiyunZhao, yanpzhan, yapei and logonoff Mar 17, 2026

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

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

openshift-ci Bot changed the title ~~[release-4.17] : Namespace is not persisting when switching to developer view from the topology page of admin page~~ [release-4.17] OCPBUGS-78673: Namespace is not persisting when switching to developer view from the topology page of admin page Mar 17, 2026

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 17, 2026

Conversation

openshift-cherrypick-robot commented Mar 17, 2026

Uh oh!

openshift-ci-robot commented Mar 17, 2026

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

logonoff left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Mar 17, 2026

Uh oh!

cajieh commented Mar 17, 2026

Uh oh!

openshift-ci-robot commented Mar 17, 2026

Uh oh!

cajieh commented Mar 17, 2026

Uh oh!

openshift-ci-robot commented Mar 17, 2026

Uh oh!

cajieh commented Mar 17, 2026

Uh oh!

openshift-ci-robot commented Mar 17, 2026

Uh oh!

logonoff commented Mar 17, 2026

Uh oh!

cajieh commented Mar 22, 2026

Uh oh!

cajieh commented Mar 23, 2026

Uh oh!

openshift-ci-robot commented Mar 25, 2026

Uh oh!

Leo6Leo commented Mar 25, 2026

Uh oh!

cajieh commented Mar 26, 2026

Uh oh!

Leo6Leo commented Mar 26, 2026

Uh oh!

Leo6Leo commented Mar 27, 2026

Uh oh!

cajieh commented Mar 28, 2026

Uh oh!

Leo6Leo commented Mar 30, 2026

Uh oh!

Leo6Leo commented Mar 31, 2026

Uh oh!

Leo6Leo commented Mar 31, 2026

Uh oh!

yapei commented Apr 1, 2026

Uh oh!

Leo6Leo commented Apr 1, 2026

Uh oh!

Leo6Leo commented Apr 1, 2026

Uh oh!

Leo6Leo commented Apr 2, 2026

Uh oh!

Leo6Leo commented Apr 2, 2026

Uh oh!

Leo6Leo commented Apr 7, 2026

Uh oh!

Leo6Leo commented Apr 7, 2026

Uh oh!

Leo6Leo commented Apr 8, 2026

Uh oh!

Leo6Leo commented Apr 8, 2026

Uh oh!

Leo6Leo commented Apr 9, 2026

Uh oh!

Leo6Leo commented Apr 9, 2026

Uh oh!

Leo6Leo commented Apr 10, 2026

Uh oh!

Leo6Leo commented Apr 13, 2026

Uh oh!

Leo6Leo commented Apr 15, 2026

Uh oh!

Leo6Leo commented Apr 17, 2026

Uh oh!

coderabbitai Bot commented Mar 17, 2026 •

edited

Loading