Jobs: jobs fail to run if --tapis-profile not set in job def despite batchSchedulerProfile set in system def

[Tyler-Clemens]

This is occurring in the PROD environment.

The system that the job is using has the batchSchedulerProfile set as "tacc":

Since the profile was already set in the system definition, the only schedulerOptions arg that was added to the job def was the account allocation. However, the job failed to load Singularity without providing a --tapis-profile arg:

When --tapis-profile is set in schedulerOptions, the module was loaded properly: