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

[lokanandaprabhu]

Fixes:
https://issues.redhat.com/browse/OCPBUGS-48491

Analysis / Root cause:
Active namespace value was not considered in namespace context

Solution Description:
Considered Active namespace value in namespace context

Screen shots / Gifs for design review:

----BEFORE---

https://drive.google.com/file/d/1VYg-pWt4ZCYKtmPx4bIK6L2Lkt3WpOPv/view?usp=sharing

---

---AFTER----

Screen.Recording.2025-03-03.at.3.38.17.PM.mov

---

Unit test coverage report:
NA

Test setup:

1. Go to topology page on ain view after login
2. Select/Create a namespace 
3. Switch to developer perspective

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

[openshift-ci-robot]

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-48491, which is invalid:

• expected the bug to target the "4.19.0" version, 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.

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

Details

In response to this:

Fixes:
https://issues.redhat.com/browse/OCPBUGS-48491

Analysis / Root cause:
Active namespace value was not considered in namespace context

Solution Description:
Considered Active namespace value in namespace context

Screen shots / Gifs for design review:

----BEFORE---

https://drive.google.com/file/d/1VYg-pWt4ZCYKtmPx4bIK6L2Lkt3WpOPv/view?usp=sharing

---

---AFTER----

Screen.Recording.2025-03-03.at.3.38.17.PM.mov

---

Unit test coverage report:
NA

Test setup:

1. Go to topology page on ain view after login
2. Select/Create a namespace
3. Switch to developer perspective

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

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.

[lokanandaprabhu]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

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.

[lokanandaprabhu]

/cc @vikram-raj

[vikram-raj]

/lgtm

[vikram-raj]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lokanandaprabhu, vikram-raj

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 [vikram-raj]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c35f1b3 and 2 for PR HEAD 1a985ff in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f5d923b and 1 for PR HEAD 1a985ff in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f5d923b and 2 for PR HEAD 1a985ff in total

[openshift-ci]

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

[openshift-ci-robot]

@lokanandaprabhu: Jira Issue OCPBUGS-48491: All pull requests linked via external trackers have merged:

• openshift/console#14812

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

Details

In response to this:

Fixes:
https://issues.redhat.com/browse/OCPBUGS-48491

Analysis / Root cause:
Active namespace value was not considered in namespace context

Solution Description:
Considered Active namespace value in namespace context

Screen shots / Gifs for design review:

----BEFORE---

https://drive.google.com/file/d/1VYg-pWt4ZCYKtmPx4bIK6L2Lkt3WpOPv/view?usp=sharing

---

---AFTER----

Screen.Recording.2025-03-03.at.3.38.17.PM.mov

---

Unit test coverage report:
NA

Test setup:

1. Go to topology page on ain view after login
2. Select/Create a namespace
3. Switch to developer perspective

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

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]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@cajieh: new pull request created: #15910

Details

In response to this:

/cherry-pick release-4.18

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.

[cajieh]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@cajieh: new pull request created: #16160

Details

In response to this:

/cherry-pick release-4.17

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.

[cajieh]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@cajieh: new pull request created: #16161

Details

In response to this:

/cherry-pick release-4.16

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.