Jenkins charm volume-map totally fails to operate properly with persistent storage.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jenkins (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
The Jenkins charm has a serious issue preventing persistent volumes from being reusable across instances of jenkins.
Steps to reproduce:
1. Deploy a jenkins instance.
2. Use volume-
3. Observe that persistent storage is being utilized and jenkins is functioning.
4. Destroy juju environment, re-bootstrap, re-deploy, re-attach persistent volume.
5. Observe that jenkins appears to work at first (records of previously run jobs exist), but then if you try to view the console output of a job or try to sign in with SSO, you get this traceback:
http://
Previously, the workaround I would use for this bug would look like this:
1. Generate a fresh nova volume *every* *time* (effectively meaning "persistent" nova volumes were single-use only).
2. Rsync just mission-critical files from one nova volume to the other, letting jenkins treat each volume like a fresh installation.
This was of course a lot of trouble as I'd have to pick and choose which files from /var/lib/jenkins to rsync.
The new workaround which is much easier is to simply delete /var/lib/