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.

Sign up for GitHub

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

Jump to bottom

Need to Log In to Stop Workspace #13971

Open
3 of 13 tasks
tsmaeder opened this issue Jul 23, 2019 · 6 comments
Open
3 of 13 tasks

Need to Log In to Stop Workspace #13971

tsmaeder opened this issue Jul 23, 2019 · 6 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@tsmaeder
Copy link
Contributor

Describe the bug

Sometimes che asks me to log in again when I want to expand the workspace management sidebar ("show navigation bar") in the top left corner. Even when I've been working in my workspace a short time before.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Expected behavior

I would not expect to have to log in at this point

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • I don't know
@nickboldt
Copy link
Contributor

Are you talking about showing the Dashboard?

@nickboldt nickboldt added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Jul 24, 2019
@nickboldt nickboldt added this to the 7.2.0 milestone Jul 24, 2019
@skabashnyuk
Copy link
Contributor

I think this issue is similar to #12099.

@tsmaeder
Copy link
Contributor Author

Yes, the problem really is that working in the IDE does not seem to count as working in the login session. The linked issue was closed because there is a workaround, as I understand. Still a problem, then.

@gazarenkov gazarenkov removed this from the 7.2.0 milestone Oct 2, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 1, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2020
@tsmaeder
Copy link
Contributor Author

tsmaeder commented Apr 1, 2020

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2020
@che-bot
Copy link
Contributor

che-bot commented Oct 1, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2020
@tsmaeder tsmaeder added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nickboldt @gazarenkov @skabashnyuk @tsmaeder @che-bot