Setting rules-update-ssh-key results in "invalid format"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Prometheus2 charm |
Fix Released
|
Undecided
|
Chris Johnston |
Bug Description
When configuring rules-update-
2023-05-08 18:20:22 WARNING unit.prometheus
2023-05-08 18:20:22 WARNING unit.prometheus
This is preventing the ability to clone the repo. If I manually add the key to the machine and then do a diff between the two files I see:
root@prometheus
38c38
< -----END OPENSSH PRIVATE KEY-----
\ No newline at end of file
---
> -----END OPENSSH PRIVATE KEY-----
root@prometheus
If I comment out the prometheus_
[1] diff prometheus.py prometheus.py.new
157,159c157,159
< with open(PATHS[
< f.write(
< os.chmod(
---
> #with open(PATHS[
> # f.write(
> #os.chmod(
238,239c238,239
< if os.path.
< os.unlink(
---
> #if os.path.
> # os.unlink(
Related branches
- Eric Chen: Approve
- 🤖 prod-jenkaas-bootstack: Approve (continuous-integration)
- BootStack Reviewers: Pending requested
-
Diff: 21 lines (+2/-1)1 file modifiedsrc/config.yaml (+2/-1)
Changed in charm-prometheus2: | |
assignee: | nobody → Chris Johnston (cjohnston) |
status: | New → Fix Committed |
Changed in charm-prometheus2: | |
milestone: | none → 23.07 |
Changed in charm-prometheus2: | |
status: | Fix Committed → Fix Released |
With help from SEG, we found out that doing `juju config prometheus2 rules-update- ssh-key= @private_ ssh_key_ file` worked, where the following did not work in my scenario:
`juju config prometheus rules-update- ssh-key= "$(cat <private_ ssh_key_ file>)" ` ssh-key= "<pasted contents of the file>"
`juju config prometheus rules-update-
This is believed to possibly be related to the way the key was generated (probably PuTTY).