Project

General

Profile

Actions

Bug #12990

closed

Add Amazon Linux support to ncf and techniques

Added by Mike Kingsbury almost 3 years ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Medium
Priority:
0

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.

Actions #1

Updated by Nicolas CHARLES almost 3 years ago

  • Target version set to 4.1.14
Actions #2

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #3

Updated by François ARMAND over 2 years ago

  • 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?

Actions #4

Updated by Mike Kingsbury over 2 years ago

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.

Actions #5

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.16 to 4.1.17
  • Priority changed from 49 to 48
Actions #7

Updated by François ARMAND over 2 years ago

  • 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)

Actions #8

Updated by Alexis MOUSSET over 2 years ago

  • 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
Actions #9

Updated by Alexis MOUSSET over 2 years ago

With 4.3.6:

AmazonLinux 
amazon_linux
amazon_linux_2018_03
Actions #10

Updated by Alexis MOUSSET over 2 years ago

Amazon Linux is not supported by our stdlib. We need code for compatibility.

Actions #11

Updated by Alexis MOUSSET over 2 years ago

  • 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
Actions #12

Updated by Alexis MOUSSET over 2 years ago

  • 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
Actions #13

Updated by Alexis MOUSSET over 2 years ago

  • Category changed from Architecture - Dependencies to Packaging
  • Target version changed from 4.1.17 to 5.0.3
Actions #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 5.0.3 to 5.0.4
Actions #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 5.0.4 to 5.0.5
Actions #16

Updated by Alexis MOUSSET over 2 years ago

  • Target version changed from 5.0.5 to 5.0.6
Actions #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 5.0.6 to 5.0.7
Actions #18

Updated by François ARMAND about 2 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #19

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions #20

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions #21

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #22

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions #23

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #24

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #25

Updated by Alexis MOUSSET over 1 year ago

  • Effort required changed from Small to Medium

This is not small.

Actions #26

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #27

Updated by Alexis MOUSSET over 1 year ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET
Actions #28

Updated by Alexis MOUSSET over 1 year ago

  • 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
Actions #29

Updated by Alexis MOUSSET over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #33

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.16 which was released today.

Actions

Also available in: Atom PDF