Bug #16246
closed
sshkeymanagement sles15 no worky
Description
same directive had worked on debian and leap42.3 etc.
using it since long.
used rudder to set a user pw to regain access.
makes me smile to know ssh failure is not a big deal with rudder.
Updated by Florian Heigl about 5 years ago
Looking into this a bit more, i can see the sshKeyDistribution reports are all missing for that node.
users' ssh directory is empty:
fhe@opensuse-leap-x64:~> ls -la .ssh/
total 0
drwx------ 1 fhe users 0 Nov 21 21:41 .
drwxr-xr-x 1 fhe users 136 Nov 21 21:41 ..
Looking at the reports, it seems like a part of the technique isn't even executed.
We can see messages about key flushes but not about the keys being managed.
E| n/a sshKeyDistribution Flush SSH file fhe The keys for user fhe were not requested to be flush
E| n/a sshKeyDistribution Flush SSH file fhe zzzzz The keys for user fhe were not requested to be flush
[snip]
Updated by Florian Heigl about 5 years ago
running "rudder agent run -i" yields this line here:
2019-11-21T22:31:04+00:00 rudder info: Deleted file '/var/rudder/tmp/check_ssh_key_distribution//fhe.authorized_keys.tmp'
Updated by Alexis Mousset about 5 years ago
- Status changed from New to Rejected
Closing, fixed by #16249
Updated by Alexis Mousset about 5 years ago
- Is duplicate of User story #16249: OpenSUSE should be detected as "suse" os family added