Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/sonarqube] Plugins no longer persist when using persistance and installing plugins via UI #12388

Closed
aaronmell opened this issue Mar 19, 2019 · 5 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@aaronmell
Copy link
Contributor

Version of Helm and Kubernetes:

Which chart:
stable/sonarqube

What happened:
when using persistance and not using the plugins: install features, the plugins are wiped away after every restart of the pod, now that the volume is mapped to the /tmp directory.

What you expected to happen:
Installing a plugin via the UI should persist the plugin after a restart.

How to reproduce it (as minimally and precisely as possible):
Install a plugin via the UI, restart the pod. Plugin is no longer installed.

Anything else we need to know:
Regression from issue #10195

@aaronmell aaronmell changed the title [stable/sonarqube] Plugins no longer persist when using persistance and not using install [stable/sonarqube] Plugins no longer persist when using persistance and installing plugins via UI Mar 19, 2019
@rjkernick
Copy link
Collaborator

/assign

@rjkernick
Copy link
Collaborator

I will try and look into this over the next few days. Thanks for reporting this

@stale
Copy link

stale bot commented Apr 27, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2019
@stale
Copy link

stale bot commented May 11, 2019

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed May 11, 2019
@ramk2020
Copy link

ramk2020 commented Jul 14, 2020

Looks like this issue does not solved. I have the same issue.

@aaronmell did you get it working? If yes, could you please help me?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants