Project

General

Profile

Actions

Bug #14421

open

SSH keys technique pre-hook need to be done just before the first directive of that technique

Added by Guillaume Tredez over 5 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

When ssh keys is deployed after new user creation, the ssh key task result in error.

I've created 2 directives in a Rule, "01 Create users" and "02 Deploy SSH keys". The "02 Deploy Ssh keys" directive fail with error 'user not exist' (previously created with Directive 01) but work when rudder launch again the Rule.

User is correctly created before ssh key deployment.

Output of rules:

2019-03-06 16:28:18    result_error    01. Test  common rules    02. Deploy common SSH keys    Flush SSH file    user3    The user user3 does not exists on this system
2019-03-06 16:28:17    result_error    01. Test  common rules    02. Deploy common SSH keys    SSH key    user3    The user user3 does NOT exist on this machine, not adding SSH key
2019-03-06 16:28:17    result_na    01. Test  common rules    01. Create common users    Home directory    user3    The user user3 doesn't need to have its home directory checked
2019-03-06 16:28:17    result_repaired    01. Test  common rules    01. Create common users    Password    user3    The user user3 ( Without any defined full name ) password was repaired
2019-03-06 16:28:17    result_repaired    01. Test  common rules    01. Create common users    Users    user3    The user user3 ( Without any defined full name ) has been added to the system

I've created 2 differents rules with 1 directive on each. User creation in first rule, ssh key in second rule and behaviour is same.

Actions

Also available in: Atom PDF