Dashboard: Viewing Config Map breaks dashboard

[alastairpat]

Environment

Installation method: kubectl apply
Kubernetes version: v1.13.7
Dashboard version: 2.0.0beta2
Operating system: macOS 10.14.5
Node.js version ('node --version' output):
Go version ('go version' output):

Steps to reproduce

1. Create a configmap with data
2. View the configmap in Kubernetes dashboard
3. Click on the 'data' section of the config map
4. Wait ~5 seconds

Observed result

The 'data' section empties. Further interactions with Dashboard are broken, with changing tabs resulting in white boxes

Expected result

The 'data' section doesn't become empty and the Dashboard continues to work

Comments

[maciaszczykm]

Can you paste logs from the browser console?

[floreks]

Console error:

As a quick workaround refresh the whole app. We will fix it.

[alastairpat]

Thanks @floreks - I put the whole development environment for our organisation onto the beta with a view to finding defects. Really appreciate the turnaround. An aside - all the end users are loving the improvements!

[maciaszczykm]

Interesting thing - it occurs only on prod, on dev everything works. Will be harder to fix.

[ElectricRabbit]

I think this issue could be connected with RBAC.
I have no issue viewing configmaps accross all namespace with ClusterRole cluster-admin
But I have reported this issue from all developers with ClusterRole assigning only [get], [list], [watch] for all cluster resources

[korroot]

This bug is still valid for 2.0.0-beta3 version - after 5 seconds showing config map the UI is frozen. User cannot edit or exit the page, needs to reload the page and exit config map tab.

Any hints how to resolve this?

[floreks]

True. Now there is a different error being thrown. I'll reopen.

/reopen
/assign @maciaszczykm

[k8s-ci-robot]

@floreks: Reopened this issue.

In response to this:

True. Now there is a different error being thrown. I'll reopen.

/reopen
/assign @maciaszczykm

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/test-infra repository.

[ivanfilippov]

This is still happening in beta4.

/reopen

[k8s-ci-robot]

@ivanfilippov: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

This is still happening in beta4.

/reopen

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/test-infra repository.

[alastairpat]

@ivanfilippov - commit eb66d229a27e9faf747ad4b7b3b94d6710aef208 containing the fix didn't make it into beta4

[mausch]

I'm still seeing this in beta5

[autherlj]

yes, still happening in beta5

[LQBing]

I reproduced this issue in beta5, but the browser console error info is different.