Bug #7100
closed
Launching twice in a row a disabled agent make the agent runs
Added by Nicolas CHARLES over 8 years ago.
Updated almost 8 years ago.
Category:
System techniques
Description
If /opt/rudder/etc/disable-agent is set, the agent is supposed to suicide itself
However, locking can get in the way, and if cf-agent is launch twice in a row, the first run locks the promise that check for the file, and the second run will hapilly ignore this file....
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 277
- Target version changed from 277 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
The Rudder cli CFEngine wrapper added in 3.1 and 3.2 checks this file before calling CFEngine (to be able to display a clear error message, and avoid a fatal error), and this issue cannot happen.
Still valid for 2.11 and 3.0.
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/940
- Target version changed from 2.11.21 to 2.11.22
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Subject changed from When the file /opt/rudder/etc/disable-agent is set, running twice in a row cf-agent (without any prameters) override the disabling to Launching twice in a row a disabled agent make the agent runs
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.22, 3.0.17, 3.1.11 and 3.2.4 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by