https://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182018-10-02T07:29:45ZIssue TrackerRudder - Bug #12866: Broken agent after updating rudder-agent to 4.3.2https://issues.rudder.io/issues/12866?journal_id=985582018-10-02T07:29:45ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Target version</strong> set to <i>4.3.5</i></li><li><strong>Severity</strong> set to <i>Critical - prevents main use of Rudder | no workaround | data loss | security</i></li><li><strong>User visibility</strong> set to <i>Operational - other Techniques | Technique editor | Rudder settings</i></li><li><strong>Priority</strong> changed from <i>0</i> to <i>73</i></li></ul><p>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.</p> Rudder - Bug #12866: Broken agent after updating rudder-agent to 4.3.2https://issues.rudder.io/issues/12866?journal_id=987752018-10-09T07:20:11ZBenoît PECCATTEbenoit.peccatte@rudder.io
<ul><li><strong>Effort required</strong> set to <i>Small</i></li><li><strong>Priority</strong> changed from <i>73</i> to <i>88</i></li></ul><p>Setting effort required to small for reproduction.<br />Solving the bug may be larger</p> Rudder - Bug #12866: Broken agent after updating rudder-agent to 4.3.2https://issues.rudder.io/issues/12866?journal_id=993452018-10-15T11:35:42ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>4.3.5</i> to <i>4.3.6</i></li></ul> Rudder - Bug #12866: Broken agent after updating rudder-agent to 4.3.2https://issues.rudder.io/issues/12866?journal_id=995032018-10-18T08:31:40ZFrançois ARMANDfrancois.armand@rudder.io
<ul></ul><p>We tried to reproduce with both centos7, debian9.5 (and ubuntu). We weren't able to reproduce (just found an issue with package methods).</p>
<p>So I can think of three reasons: <br />- 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), <br />- 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)<br />- the bug was corrected (as a side effect) in last 4.3 (so bad we don't know why).</p>
<p>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.</p> Rudder - Bug #12866: Broken agent after updating rudder-agent to 4.3.2https://issues.rudder.io/issues/12866?journal_id=996622018-10-23T07:09:59ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Priority</strong> changed from <i>88</i> to <i>87</i></li></ul><p>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.</p>