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

Dashboard does not respect CheCluster CR changes #21654

Closed
Tracked by #20549
tolusha opened this issue Aug 24, 2022 · 4 comments · Fixed by eclipse-che/che-dashboard#628
Closed
Tracked by #20549

Dashboard does not respect CheCluster CR changes #21654

tolusha opened this issue Aug 24, 2022 · 4 comments · Fixed by eclipse-che/che-dashboard#628
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@tolusha
Copy link
Contributor

tolusha commented Aug 24, 2022

Describe the bug

Dashboard does not respect CheCluster CR changes

Che version

next (development version)

Steps to reproduce

  1. Deploy Eclipse Che
  2. Update CheCluster CR to set openVSXURL
  3. Dashboard still uses an old value

Expected behavior

Dashboard uses a new openVSXURL field value

Runtime

minikube

Screenshots

No response

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@tolusha tolusha added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard labels Aug 24, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 24, 2022
@Kasturi1820 Kasturi1820 added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 24, 2022
@benoitf
Copy link
Contributor

benoitf commented Aug 24, 2022

Here my workaround was to delete dashboard pod (so it's started again and fetch/keep in its cache the good value)
But yes I was expected that on CheCluster change the value is updated/cache invalidated

@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Aug 25, 2022
@ibuziuk ibuziuk mentioned this issue Aug 25, 2022
82 tasks
@olexii4 olexii4 self-assigned this Aug 29, 2022
@olexii4
Copy link
Contributor

olexii4 commented Aug 29, 2022

@benoitf I cannot reproduce this issue
https://youtu.be/AVGG1STrvrQ

PS
I tested it with the platform minikube

@benoitf
Copy link
Contributor

benoitf commented Sep 1, 2022

It's still actual

image

image

we can clearly see that plug-in registry pod has been restarted but not the dashboard and we still have the previous value of the CheCluster

image

so dashboard is still applying the wrong value

@olexii4
Copy link
Contributor

olexii4 commented Sep 4, 2022

It's still actual

image

image

we can clearly see that plug-in registry pod has been restarted but not the dashboard and we still have the previous value of the CheCluster

image

so dashboard is still applying the wrong value

@benoitf I created the video on how the dashboard used and applied the new openVSXURL during the creation of new workspaces.

Do you expect the dashboard should check and update the environment variables on all created workspaces?

Could you clarify the steps to reproduce?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants