Bug #4194
closed
Rudder can't correctly check processes on *VZ system if there is no vzps
Description
When there is no vzps installed on the system (which is quite common on standard vz system), CFEngine falls back to standard ps command, and thus cannot properly check processes in any Techniques
Olivier made a script, that could be automatically deployed on VZ host if there is no vzps available, to be able to correctly use process promise type.
Files
Updated by Nicolas CHARLES over 10 years ago
And we could add a patch in our version of CFEngine to look in a specific location (Rudder related, for instance /opt/rudder/bin) for this script if the file /bin/vzps is not there
Updated by Olivier Mauras over 10 years ago
What would be the easier/less intrusive? Patch cfengine to look for another location or deploy /bin/vzps from tools/ if missing?
I guess deploying it, adds the need to take care of removing it on rudder-agent removal...
Anyway please find the script attached.
Updated by Nicolas CHARLES over 10 years ago
Less intrusive would be to patch our cfengine to look for another location; as it's not really neat to change the content of /bin folder
Updated by Nicolas CHARLES over 10 years ago
Ticket have been created/updated on CFEngine bug tracket to be able to configure which command to use for PS
https://cfengine.com/dev/issues/3828
https://cfengine.com/dev/issues/3395
Updated by Jonathan CLARKE over 10 years ago
- Category changed from 13 to System techniques
- Status changed from New to 8
- Priority changed from N/A to 2
- Target version changed from 2.6.10 to 2.9.0~rc1
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.0~rc1 to 2.9.0~rc2
THis won't be done ine 2.9.0~beta1
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.0~rc2 to 2.9.0
Delayed to 2.9 finale release
Updated by François ARMAND over 10 years ago
- Target version changed from 2.9.0 to 2.10.0~beta1
Missed the 2.9.0 release.
Updated by François ARMAND over 10 years ago
I'm wondering why this was retargeted from 2.6 to 2.9, and if there was some reason linked to the fact that it must go into a non released version, if we really want to wait 2.10 for that.
Jon, Nico: some ideas ?
Updated by Jonathan CLARKE over 10 years ago
François ARMAND wrote:
I'm wondering why this was retargeted from 2.6 to 2.9, and if there was some reason linked to the fact that it must go into a non released version, if we really want to wait 2.10 for that.
Jon, Nico: some ideas ?
Yup, this is a pretty impacting change, it should go in a new version.
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.0~beta1 to 2.10.0
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.0 to 2.11.0~beta1
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.11.0~beta1 to 2.11.0~beta2
Updated by Matthieu CERDA almost 10 years ago
- Target version changed from 2.11.0~beta2 to 2.11.0~rc1
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.11.0~rc1 to 2.11.0~rc2
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.11.0~rc2 to 2.11.0
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.11.0 to 2.11.1
Updated by Nicolas PERRON almost 10 years ago
- Target version changed from 2.11.1 to 2.11.2
Updated by Nicolas PERRON over 9 years ago
- Target version changed from 2.11.2 to 2.11.3
Updated by Matthieu CERDA over 9 years ago
- Target version changed from 2.11.3 to 2.11.4
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.11.4 to 2.11.5
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.11.5 to 2.11.6
Updated by Nicolas CHARLES over 9 years ago
- Status changed from 8 to Rejected
This was fixed in #5477
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.6 to 2.11.7