with upcoming 5.0 release, we need to ensure that kickstart calls out to right pegasus-integrity ( the one in the same install as where kickstart is). this is required because jobs will land on a worker nodes where 4.9 is installed by default, and a callout to 4.9 pegasus-integrity fails. this leads to the checksums not being generated.

so, the agreed order in kickstart for discovery of executable is

• bin directory of the install from where pegasus-kickstart is invoked, unless PEGASUS_HOME is defined in the environment.

currently some of the workflow tests fail with these symptoms
https://bamboo.isi.edu/browse/PEGASUS-WT50-T33B-529/log