Bug #4194: Rudder can't correctly check processes on *VZ system if there is no vzps - Rudder - Issue Tracker

Actions

Copy link

Bug #4194

closed

Rudder can't correctly check processes on *VZ system if there is no vzps

Added by Nicolas CHARLES almost 11 years ago. Updated almost 10 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

System techniques

Target version:

2.11.7

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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

vzps (2.09 KB) vzps

Olivier Mauras, 2013-11-26 10:50

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 11 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

Actions

Copy link

Updated by Olivier Mauras almost 11 years ago

File vzps vzps added

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.

Actions

Copy link

Updated by Nicolas CHARLES almost 11 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

Actions

Copy link

Updated by Nicolas CHARLES almost 11 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

Actions

Copy link

Updated by Jonathan CLARKE almost 11 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

Actions

Copy link

Updated by Vincent MEMBRÉ almost 11 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

Actions

Copy link

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.9.0~rc2 to 2.9.0

Delayed to 2.9 finale release

Actions

Copy link

Updated by François ARMAND almost 11 years ago

Target version changed from 2.9.0 to 2.10.0~beta1

Missed the 2.9.0 release.

Actions

Copy link

Updated by François ARMAND almost 11 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 ?

Actions

Copy link

#10

Updated by Jonathan CLARKE almost 11 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.

Actions

Copy link

#11