puppetlabs / puppetlabs/puppetlabs-sshkeys_core
sshkeys removed in all puppet runs
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I'm using now the old version 1.0.2 of the module. I am trying to update to latest 2.5.0, but when I used in Ubuntu 18.04 and Ubuntu 20.04 clients, I get messages like:
Notice: /Stage[main]/Ssh/Sshkey[piscis22.um.es_ed25519@]/ensure: removed (corrective)
Notice: /Stage[main]/Ssh/Sshkey[sorex20.um.es_rsa@]/ensure: removed (corrective)
Notice: /Stage[main]/Ssh/Sshkey[mustela33.um.es_rsa@]/ensure: removed (corrective)
Notice: /Stage[main]/Ssh/Sshkey[fiber10.um.es_rsa@]/ensure: removed (corrective)
...
for all the entries in /etc/ssh/ssh_known_host in all puppet runs (although entries are not currently removed and it shouldn't)
In newer versions of Ubuntu I don't have this problem
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Puppet 2.5.0 run on Ubuntu 18.04 and 20.04, focusing on the reported entries under /etc/ssh/ssh_known_host and the corrective removal notices. Compare the behavior with version 1.0.2 and newer Ubuntu versions; done means explaining why existing keys are reported as removed and preventing the false notices without removing entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100