Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 599037 - configd.py on windows run_cmd causes .dll failure on execute
configd.py on windows run_cmd causes .dll failure on execute
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby (Show other bugs)
All Windows
low Severity medium
: 1.3
: ---
Assigned To: Robert Rati
Martin Kudlej
Depends On:
Blocks: 559596
  Show dependency treegraph
Reported: 2010-06-02 11:01 EDT by Timothy St. Clair
Modified: 2010-10-20 07:35 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-10-20 07:33:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Timothy St. Clair 2010-06-02 11:01:39 EDT
Description of problem:
When the configd shells out using run_cmd it appears that the executed command fails, from what looks to be a PATH issue.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. disable wallaby and broker run condor_configd.py

Actual results:
pop-up saying it could not initialize condor_config_val

Expected results:
non pop-up, clean run

Additional info:
condor_config_val -dump runs cleanly from the command line.  The only thing that I'm aware of that can cause an issue such as this is if run_cmd is not using system PATH env.
Comment 1 Robert Rati 2010-06-03 18:36:55 EDT
This was an issue with the jobhooks python package from condor-job-hooks.  The run_cmd function tries to be safe and use a very limited set of env variables.  However, condor_config_val on windows needs more than a bare minimum to work in some cases.

Fixed in:
Comment 5 Martin Kudlej 2010-09-27 08:43:35 EDT
I've tested this on Windows 2003/XP x i386/x86_64 and it works. -->VERIFIED

Note You need to log in before you can comment on or make changes to this bug.