Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: CSI namespace bugs #7896

Merged
merged 2 commits into from
May 11, 2020
Merged

UI: CSI namespace bugs #7896

merged 2 commits into from
May 11, 2020

Conversation

DingoEatingFuzz
Copy link
Contributor

This builds off of #7895. Only the last two commits are original. This should be rebased and merged second.

There were a couple namespace quirks that the UI wasn't handling well. The combination of the two meant it was impossible to view CSI volumes for any namespace other than Default unless you put the namespace query param in the URL 😳

Bug 1: Switching namespaces shouldn't always redirect to Jobs

This made sense when Jobs were the only namespace-sensitive resource, but volumes are too. Now the UI will reset to the Jobs list for the Volumes list depending on where you are in the app. If you are on a storage page, go to volumes, otherwise, go to jobs.

Bug 2: Setting a namespace on the Volumes or Jobs page didn't carry over to the other page

Switching to, say, Namespace 1 when looking at jobs successfully sets the active namespace to Namespace 1, but if you then click on the Storage nav link, the namespace is reset to Default since they have independent query params. Now the namespace query param is provided in the gutter menu link-tos

Since switching namespaces means being forced to the jobs page, and then revisiting storage means resetting the namespace back to Default, you can see how the two bugs work in concert to lock people out of seeing non-default namespaced volumes.

@DingoEatingFuzz DingoEatingFuzz requested review from backspace and a team May 8, 2020 04:49
Copy link
Contributor

@backspace backspace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pending the rebase, I reviewed using this comparison URL. This looks good to me, a clean and well-tested intervention.

Changing namespaces can be done anywhere in the app even though many
Nomad resources aren't namespace-sensitive (e.g., clients, plugins).

A user changing namespaces is an intent to reset context, "now I want
to begin a task that relates to Namespace X". Where that task begins
used to always be the Jobs list, since it was the only namespace
sensitive resource. Now with CSI Volumes, "square 1" is Volumes if the
namespace is changed from a storage page.
@DingoEatingFuzz DingoEatingFuzz force-pushed the f-ui/csi-namespace-issue branch from 6427dcb to 804029c Compare May 9, 2020 00:35
@DingoEatingFuzz DingoEatingFuzz merged commit bda9e84 into master May 11, 2020
@DingoEatingFuzz DingoEatingFuzz deleted the f-ui/csi-namespace-issue branch May 11, 2020 16:22
@github-actions
Copy link

github-actions bot commented Jan 6, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants