Bug #12990
closed
Add Amazon Linux support to ncf and techniques
Added by Mike Kingsbury over 6 years ago.
Updated almost 5 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Description
The underlying version of CFEngine 3.10 does not detect Amazon Linux, and as a result some variables pointing to tool paths are undefined. This leads to the technique failures. I discovered this with sshKeyDistribution, as ${paths.sed} was not defined. CFEngine 3.11 (and later) appears to have code changes to properly detect Amazon Linux.
It appears Architecture #12856 is in progress to incorporate CFengine 3.12 in release 4.4.0.
A workaround for me was to create a /etc/redhat-release file with the contents I took from a CentOS host ("CentOS Linux release 7.3.1611 (Core)"). After creating the file, the agent detected it as CentOS and the sshKeyDistribution techniques worked and reported properly.
- Target version set to 4.1.14
- Target version changed from 4.1.14 to 4.1.15
- Priority changed from 50 to 49
Mike, we switched to CFEngine 3.12 in Rudder 5.0.0, which is released this week. Would you mind test with that version to see it corrects you problem?
No, it doesn't appear so. Operating system from the WebUI (4.3.4 server w/ 5.0-rc1 client) shows \S
The actual failure for the sshKeyDistribution still remains. I haven't had time to figure out more details as the cause, but I suspect its still the undefined paths.sed.
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- Priority changed from 49 to 48
- Effort required set to Very Small
- Priority changed from 48 to 76
OK, we need to check if it's still not OK in 5.0.1 (that's a very small required effort)
- Priority changed from 76 to 0
5.0.2 on Amazon Linux gives:
AmazonLinux
amazon_linux
amazon_linux_2018_03
amzn
amzn_2018
amzn_2018_03
With 4.3.6:
AmazonLinux
amazon_linux
amazon_linux_2018_03
Amazon Linux is not supported by our stdlib. We need code for compatibility.
- Subject changed from RHEL/CentOS-based Amazon Linux fails detection with Rudder agent 4.3.2, resulting in technique failures to Add Amazon Linux support to ncf and techniques
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Effort required changed from Very Small to Small
Should be close to RHEL, but requires:
- contributing stdlib compatibility upstream
- Fix ncf
- Fix techniques
- Category changed from Architecture - Dependencies to Packaging
- Target version changed from 4.1.17 to 5.0.3
- Target version changed from 5.0.3 to 5.0.4
- Target version changed from 5.0.4 to 5.0.5
- Target version changed from 5.0.5 to 5.0.6
- Target version changed from 5.0.6 to 5.0.7
- Target version changed from 5.0.7 to 5.0.9
- Target version changed from 5.0.9 to 5.0.10
- Target version changed from 5.0.10 to 5.0.11
- Target version changed from 5.0.11 to 5.0.12
- Target version changed from 5.0.12 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Target version changed from 5.0.14 to 5.0.15
- Effort required changed from Small to Medium
- Target version changed from 5.0.15 to 5.0.16
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1573
- Status changed from Pending technical review to Pending release
- Name check set to To do
- Fix check set to To do
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.16 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by