Project

General

Profile

Actions

Bug #11937

closed

yum is run at each cf-promises, having a massive perf cost, on redhat-like system

Added by Nicolas CHARLES almost 7 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

On redhat like system, at each cf-promises (but also at each cf-server restart), we run the command

LANG=C /usr/bin/yum --setopt=exit_on_lock=True 2>&1 | /bin/grep -q -E '(Command line error: no such option: --setopt|Main config did not have a exit_on_lock attr. before setopt)'

it goes without saying that it has a huge perf cost (0,5 s CPU on a test platform, about a third of total cf-promises run)

we could guard the execution by a simple "agent" class, and have easy gain

Actions #1

Updated by Nicolas CHARLES almost 7 years ago

  • Status changed from New to In progress
Actions #2

Updated by Nicolas CHARLES almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/ncf/pull/675
Actions #3

Updated by Rudder Quality Assistant almost 7 years ago

  • Assignee changed from Alexis Mousset to Nicolas CHARLES
Actions #4

Updated by Nicolas CHARLES almost 7 years ago

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

Updated by Vincent MEMBRÉ almost 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Actions #6

Updated by Alexis Mousset over 2 years ago

  • Project changed from 41 to Rudder
  • Category changed from Generic methods to Generic methods
Actions

Also available in: Atom PDF