StandardError - The task could not be started within the maintenance window - While running remote execution job Through Red Hat Satellite 6 on Host Collections.

Environment

• Red Hat Satellite 6

Issue

• Remote execution job fails for few hosts when executed on Host Collection. For few hosts it works fine.

Resolution

• Either remove the customize value of Concurrency and Timeout to kill from advance settings of job or set the correct Concurrency and Timeout to kill as per the no. of host machines.

• For more info on Concurrency and Timeout to kill follow this documentation

For more KB articles/solutions related to Red Hat Satellite 6.x Remote Execution Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Remote Execution Issues

Root Cause

• If a custom value for Concurrency and Time Span in job settings tab has been set.

• If remote execution job is executed on a host collection of 20 machines. However in Concurrency Level only 2 is defined. Then at once only job would be executed on 2 machines out of 20. It might take long time to finish the job for these 2 machines. Other 18 machines might fail in that case after waiting for a particular period of time as per the time span.

Diagnostic Steps

• Verify in the advance setting of this job that is there any customize setting for Concurrency and Time Span .

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.