Project

General

Profile

Actions
Copy link

Bug #4923

closed

Bug #4613: When multiples cf-execd are running at the same time, agent is not behaving properly, and node is in NoAnswer state

check-rudder-agent is broken on 2.9 nightly because of a bad merge

Added by Nicolas CHARLES over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
2.9.5
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I messed up the merge 2.6 -> 2.9, and the check-rudder-agent script now has a <<<<<<< HEAD in it
It must be fixed

Actions
Copy link
 #1

Updated by Nicolas CHARLES over 10 years ago

  • Project changed from Rudder to 34
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/336
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:a2a3f3edc69c2afaca02c867d5141cf3b4a27528.

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 10 years ago

  • Project changed from 34 to Rudder
  • Category set to System integration
  • Parent task set to #4613
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.9.5 (announcement , changelog) and 2.10.1 (announcement , changelog), which were released today.

Actions
Copy link

Also available in: Atom PDF