Step loaded with .load executes but no step logs produced
Using BF 7.1.2 and the .load command to dynamically create a step. The .load command succeeds (1 step loaded) and the new step executes successfully. There's even a step following the loaded step and it executes successfully.
Here's the problem: There are no step logs produced for the loaded step. I know it executes because all does is "touch myfile" and "myfile" does in fact exist in the job path on the agent server.
Anyone else experienced this issue where there are no step logs produced when a loaded step executes?
Here's the problem: There are no step logs produced for the loaded step. I know it executes because all does is "touch myfile" and "myfile" does in fact exist in the job path on the agent server.
Anyone else experienced this issue where there are no step logs produced when a loaded step executes?
3 answers
Using BF 7.1.2 and the .load command to dynamically create a step. The .load command succeeds (1 step loaded) and the new step executes successfully. There's even a step following the loaded step and it executes successfully.
Here's the problem: There are no step logs produced for the loaded step. I know it executes because all does is "touch myfile" and "myfile" does in fact exist in the job path on the agent server.
Anyone else experienced this issue where there are no step logs produced when a loaded step executes?
I've not seen this happen. If there is no step log at all (even the env var setup) then you may have something that needs support attention and should open a PMR.