Issue encountered by @AndrewHazelton, and reported to Jet system Admin. And the following are adapted from the email from Jet Admin:
During the Jet downtime yesterday we upgraded Slurm to version 23.11.1, which caused a problem with Rocoto not being able to get the STATUS for jobs. Rocoto workflows running after the Jet downtime may have problems and fail with the "state" being "UNAVAILABLE". This morning the default version of Rocoto was updated to version rocoto/1.3.6 to fix this problem.
Please switch ASAP to this latest default version of Rocoto in your interactive and batch scripts, and also please check your crontab entries to make sure you are not using the older version!
BinLiu-NOAA
commented
7 months ago
Description
Issue encountered by @AndrewHazelton, and reported to Jet system Admin. And the following are adapted from the email from Jet Admin:
During the Jet downtime yesterday we upgraded Slurm to version 23.11.1, which caused a problem with Rocoto not being able to get the STATUS for jobs. Rocoto workflows running after the Jet downtime may have problems and fail with the "state" being "UNAVAILABLE". This morning the default version of Rocoto was updated to version rocoto/1.3.6 to fix this problem.
Please switch ASAP to this latest default version of Rocoto in your interactive and batch scripts, and also please check your crontab entries to make sure you are not using the older version!
"Best Practices" for using Rocoto are found here: https://rdhpcs-common-docs.rdhpcs.noaa.gov/wiki/index.php?title=Rocoto_-_The_Workflow_Manager#Rocoto_Best_Practices
Additional context (optional)