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

Diff Editor no longer works with version 2.10.0 #7704

Open
ILZ1105 opened this issue Apr 16, 2024 · 2 comments
Open

Diff Editor no longer works with version 2.10.0 #7704

ILZ1105 opened this issue Apr 16, 2024 · 2 comments
Labels
kind/bug An issue that reports a defect in an existing feature

Comments

@ILZ1105
Copy link

ILZ1105 commented Apr 16, 2024

Describe the bug
The Diff Editor to compare modified values with the package values no longer works. It doesn't compare the values anymore, it only shows the already modified values with the potential new values of the Helm but there is no comparison (red/green) anymore.

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade from 2.8.0 to 2.10.0
  2. Try upgrading any deployed application within kubeapps and the check the diff editor (you can even use kubeapps itself)
  3. No green/red lines will show up anymore

Expected behavior
Diff editor still shows the red/green lines for comparison.

Screenshots
None

Desktop (please complete the following information):

  • Kubeapps Version 2.10.0
  • Kubernetes version 1.26.5
  • Package version Helm Chart 15.0.2

Additional context
None

@ILZ1105 ILZ1105 added the kind/bug An issue that reports a defect in an existing feature label Apr 16, 2024
@antgamdia
Copy link
Contributor

Thanks for reporting it; it is odd since we have some automatic e2e tests checking the diff view, but we will look into it soon.

@ILZ1105
Copy link
Author

ILZ1105 commented Apr 16, 2024

It's odd indeed, I was checking through the logs to find any kind of error but it's a bit tricky as I have numerous issues at once with 2.10.0 that I'm still looking into. One of the bigger issues seems to relate to postgresql #7702 which caused quite a bunch of problems with synching the repos. I even had to manually delete the entry in the DB of the synched repo (the hash value) to be able to sync bitnami again. I rolled back to 2.8.0 and upgraded to 2.10.0 again and it was fine this time, though the DB was still overloaded because I couldn't increase the CPU for it as described in the bug.

There might be a chance it's related to that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug An issue that reports a defect in an existing feature
Projects
Status: 🗂 Backlog
Development

No branches or pull requests

2 participants