Project

General

Profile

Actions
Copy link

Bug #26983

open

Almalinux 9.x in a technique condition fails

Added by Nicolas Pawlak 3 days ago. Updated 3 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
-
Target version:
-
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Hi,

I'm trying to create on Rudder 8.3.1 a technique with a condition for applying only on AlmaLinux 9.x.

I choose "AlmaLinux" in "Operating system", but when I specify "9" in "Major version", the OS automatically switch to CentOS ("applied configuration expression: centos_9"). And... the rule fails: "Skipping method 'File content' with key parameter '/folder/file' since condition 'centos_9' is not reached was not applicable".

If i choose "AlmaLinux" but without major or minor version, the OS don't switch, applied configuration expression stays with "almalinux" and the rule works (Insert content into /folder/file was repaired). But I can't restrict to AlmaLinux 9, for example.

I don't reproduce this one for other Linux OS : I can specify Debian 11.x or 12.11, Ubuntu 22.10 or 24.04... but with AlmaLinux, if I want to restrict to a specific version, it's saved like CentOS and the rule don't work.

Thanks.

Actions
Copy link
 #1

Updated by Nicolas Pawlak 3 days ago

  • Description updated (diff)
Actions
Copy link

Also available in: Atom PDF