Project

General

Profile

Actions

Bug #12866

closed

Broken agent after updating rudder-agent to 4.3.2

Added by I C over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Agent
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
87
Name check:
Fix check:
Regression:

Description

Hi,

Last week I have updated all my rudder-agent nodes with rudder.

To do this, I use a directive from the "package source and settings (APT)" technique (in v3.1) to update the rudder repository for debian like nodes and a directive from the "File Download (rudder server)" technique (in v2.1) for redhat like nodes.

Next, I use a directive from the "packages" technique (in v1.1) to keep rudder-agent to the "latest available version".

When the agent was updated on my nodes during the next agent execution, i have lost a lot of reports and after a little inspection I have found that the rudder-agent package was not correctly updated on debian and centos nodes.

It is very strange because not all of my nodes was impacted.

For now, I can tell that :
- Every debian 9 was impacted
- Many centos 7 was impacted

The rudder-agent package was updated from 4.2.6 to 4.3.2.

You can find more technical information in attachement.

Thanks for your help


Files

debian-logs (5.22 KB) debian-logs I C, 2018-07-02 13:31
centos-logs (2.43 KB) centos-logs I C, 2018-07-02 13:31
Actions

Also available in: Atom PDF