Actions
Bug #14963
closed
SSH key distribution fails
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
On a rudder 5.0 I tried to deploy a new ssh key to a user without any .ssh/authorized_keys defined.
I had already another directive handling ssh keys for other user, applied on this node.
At execution time, I have no report for the new directive and I only have an error prompt like:
error: Failed to chdir into '/var/rudder/tmp/check_ssh_key_distribution'. (chdir: 'No such file or directory') error: Promised to edit '/var/rudder/tmp/check_ssh_key_distribution//vincent.membre.authorized_keys.tmp', but file does not exist error: Method 'check_ssh_key_distribution_4_0_497ba345_ee17_4622_af54_20dbe0d9048f' failed in some repairs
Updated by Félix DALLIDET over 5 years ago
The "other" directive was in 3.0 with the flushing key option set.
The "new" one was in 4.0 without the option set.
Migrating the "new" one to 3.0 fixed the issue. I guess that we are now handling the flushing the same way between 3.0 and 4.0 which break the compatibility
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset almost 5 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by François ARMAND over 4 years ago
- Related to Bug #16516: No flush key report on sshKeyDistribution when there is not yet an ssh key configured added
Updated by François ARMAND over 4 years ago
- Status changed from New to Rejected
I'm closing that one as a duplicate of #16516 (I added details there)
Actions