Project

General

Profile

Actions

Bug #8620

closed

Bundle "fetchFusionTools": bug in OS version check

Added by Dmitry Svyatogorov almost 8 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Medium
Priority:
20
Name check:
Fix check:
Regression:

Description

Bundle "fetchFusionTools" explores linux version basing on weak criterias. (In other places, things are doing well.)

Rudder agent 3.2.4-trusty0 (CFEngine Core 3.7.1) (prepackaged from http://www.rudder-project.org/apt-3.2/) @ Ubuntu 14.04.3 LTS

#echo "Red Hat Enterprise Linux Server release 6.5 (Santiago)" > /etc/redhat-release
#rudder agent run -v > rudder.log
…bundle fetchFusionTools
…
rudder  verbose: P:    Base context class: redhat
rudder  verbose: P:    Container path : '/default/rudder_system_directives/methods/'Rudder system policy: daily inventory/Inventory'/default/fetchFusionTools/packages/'curl'[0]'
rudder  verbose: P:
rudder  verbose: P:    Comment:  Installing curl using yum

Yes, it considers RHEL onboard (instead of ubuntu) and stucks with trying to implement yum!
Since now, inventory task newer succeeds (but reports are sending, but at each agent pass, despite reporting settings).

  • Why "/etc/redhat-release" on debian|ubuntu at all? Because of vendor's HW support "nuances"…
Actions #1

Updated by Alexis Mousset almost 8 years ago

  • Category changed from Techniques to Agent
  • Target version changed from 3.2.5 to 2.11.23

This detection is done by CFEngine, which defines the classes for all detected OSes (in your case, ubuntu AND redhat), which causes fetchFusionTools to try to install a package using yum, and it probably breaks a lot of other things in the techniques.

When you say that in some parts, things are doing well, to which parts are you referring to? Which criteria do you you would be better?

Actions #2

Updated by Dmitry Svyatogorov almost 8 years ago

Hmmm… The subsequent bundles are built from "Package management for Debian / Ubuntu / APT systems", so, You are right (apt of course uses apt-*).
But why not just to check for available package manager inside linux db (e.g. "which yum" "which apt-get" "which zypper")? Such check will exponentially reduce the chance of mistake.
It seems to be a very rare case to find a couple of package managers on single host.

Actions #3

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #4

Updated by Alexis Mousset over 7 years ago

  • Category changed from Agent to System techniques
Actions #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #11

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #12

Updated by Benoît PECCATTE about 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority set to 0

It also seems to be very rare to have a /etc/redhat-release on ubuntu

Actions #13

Updated by François ARMAND about 7 years ago

  • Effort required set to Medium
  • Priority changed from 0 to 22

We could use lsb_release when available, which is always (AFAIK) the case on ubuntu. There will always be edge cases, thought.

Actions #14

Updated by Benoît PECCATTE about 7 years ago

  • Priority changed from 22 to 21
Actions #15

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #16

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
  • Priority changed from 21 to 20
Actions #17

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #18

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #19

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #20

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #21

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #23

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #24

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #25

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #26

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #27

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #28

Updated by Benoît PECCATTE over 5 years ago

  • Status changed from New to Rejected

We removed fetchFusionTools

Actions

Also available in: Atom PDF