Grafana install fails with default config due to GPG key rotation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Grafana Charm |
Fix Released
|
High
|
Mert Kirpici |
Bug Description
The gpg signing key for grafana was recent rotated: https:/
This causes installation to fail with the default config now.
A workaround:
```
$ juju config grafana install_keys="- |
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQGNBGTnhmk
mcKlGDU0ugo
k44UOetRtV9
Ef3NChlOh2Z
CBLPWitKRMn
Dts4PNx4Wr9
JS4HGxFFjSk
Bb16nwJ8bMD
eTaXvc4glM9
YW5hLmNvbT6
AwUJA8JnAAU
i+xytv2keEF
GuMsjHWgat5
B0HHIj2wI9k
8FW9EU0HM0t
mnWQQhhS6BO
ocQcAJA8HFT
7FvSiV0eXId
q1xdW0+
AY0EZOeGaQE
FDEXstjJQQ1
D56yYxqGY0Y
8JvvSq9xbsK
7mlQnzQo9z4
3zht8luFOYp
nm4OQvBA9Df
y3csE059YVI
haViRS5v/
AmTnhmkCGww
LNgci7z7smX
xTyR31ARENM
lkLxUTiB43o
2ZriF56uPer
9iqi3fG3iSb
TWWWseSQkHR
9O/
SR+
=J9CI
-----END PGP PUBLIC KEY BLOCK-----
"
$ juju config grafana install_
```
Related branches
- Erhan Sunar (community): Approve
- Eric Chen: Approve
- 🤖 prod-jenkaas-bootstack (community): Approve (continuous-integration)
-
Diff: 109 lines (+40/-44)2 files modifiedsrc/config.yaml (+39/-39)
src/wheelhouse.txt (+1/-5)
- 🤖 prod-jenkaas-bootstack (community): Needs Fixing (continuous-integration)
- BootStack Reviewers: Pending requested
- BootStack Reviewers: Pending requested
-
Diff: 96 lines (+39/-39)1 file modifiedsrc/config.yaml (+39/-39)
Changed in charm-grafana: | |
assignee: | nobody → Samuel Walladge (swalladge) |
status: | New → In Progress |
summary: |
- Grafana install fails with default config + Grafana install fails with default config due to GPG key rotation |
Changed in charm-grafana: | |
importance: | Undecided → High |
tags: | added: bseng-1512 |
Changed in charm-grafana: | |
assignee: | Samuel Walladge (swalladge) → nobody |
Changed in charm-grafana: | |
assignee: | nobody → Mert Kirpici (mertkirpici) |
Changed in charm-grafana: | |
milestone: | none → 23.10 |
Changed in charm-grafana: | |
status: | Fix Committed → Fix Released |
Hi there Samuel, I did supersede your MP with the additional commit that fixes the build problem. I cherry-picked your commit to keep all your work intact. It was necessary since neither of the two fixes can produce a green CI job alone. There are intermittent issues with the CI, which should hopefully be resolved today and this will get merged.
Thanks for the patch.