Environment
Novell ZENworks 10 Configuration Management
Situation
Deployment or Discovery tasks may stay in pending until loader is restarted or task is aborted and restarted.
After an upgrade to ZCM 10.0.1 the discovery task in ZCM (all methods) and choosing to run immediately, status will to a pending state and hang there until the ZENloader service is restarted or the server is rebooted.
After an upgrade to ZCM 10.0.1 the discovery task in ZCM (all methods) and choosing to run immediately, status will to a pending state and hang there until the ZENloader service is restarted or the server is rebooted.
Resolution
This is fixed in version 10.0.3 - see KB 3486285 "Updates to ZENworks 10 Configuration Management" which can be found at https://www.novell.com/support
Additional Information
In the case of Deployment tasks, the issue is consistent when the task is created with "no schedule" and then launched manually from action tab. The failure occurs on first attempt to launch the task.
loader-messages log showed the following after manual launch attempt:
[DEBUG] [4/11/08 1:54:39 PM] [] [Loader.DeploymentModule] [FINER: Task schedule is empty. Will not schedule task: noScheduleTask] [FINER: Task schedule is empty. Will not schedule task: noScheduleTask] [] []