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):
Steps to Reproduce:
1. disable wallaby and broker run condor_configd.py
pop-up saying it could not initialize condor_config_val
non pop-up, clean run
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.
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.
I've tested this on Windows 2003/XP x i386/x86_64 and it works. -->VERIFIED