Bug #12866
closedBroken agent after updating rudder-agent to 4.3.2
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
Updated by François ARMAND about 6 years ago
- Target version set to 4.3.5
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 73
So, something has disabled the agent on these distribution. We don't have any idea - for now - about what caused that. We are looking at it.
Updated by Benoît PECCATTE about 6 years ago
- Effort required set to Small
- Priority changed from 73 to 88
Setting effort required to small for reproduction.
Solving the bug may be larger
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.3.5 to 4.3.6
Updated by François ARMAND about 6 years ago
We tried to reproduce with both centos7, debian9.5 (and ubuntu). We weren't able to reproduce (just found an issue with package methods).
So I can think of three reasons:
- it's a bug that occures only from a specific version of 4.2 to a specific 4.3. In that case, I would say it could be closed (because these versions are not supported anymore),
- it's a bug that occures with some condition are met on the node, and we don't know which (and we didn't reach that state)
- the bug was corrected (as a side effect) in last 4.3 (so bad we don't know why).
I'm not sure we will be able to advance on that ticket without a process to reproduce, but the bug is awful, and I would hate to let it slip through if it is not corrected yet.
Updated by François ARMAND about 6 years ago
- Status changed from New to Rejected
- Priority changed from 88 to 87
I'm closing that one because we are not able to reproduce it. If anybody has the same problem, please tell us what are your exact sourece version (os, rudder agent, rudder server), what are the target versions, what is the exact configuration of technique used.