the logs look perfectly fine.
35 Patches have been deployed.... All of them came back with Exit-Code 3010 as they require a reboot.
Your server seems to have rebooted and the end and all should be fine.
Which Error did you see in the console that indicates the job failed ?
I recall there was an issue in older versions which would cause this "Failed to create configuration file" error to occur if the reboot did not actually begin 60 seconds after being initiated. The bldeploy initiates the reboot and waits for 60 seconds. If the system is too busy, and does not have a chance to close all running processes within 60 seconds, bldeploy thinks that the reboot cannot happen and fails, while in reality the reboot does happen just a bit later. In the fix we extended the wait period from 60 seconds to 15 minutes. Can you confirm your agent version?
Thanks for the information.
The version we are using is: BladeLogic RSCD Agent 8.3.00.115 (Release) [Jan 11 2013 13:59:25]
Is the wait time for reboot is extended/changed after this version?
Could you please attache or See the log file for the patch in \WINNT or \WINDOWS on the target, and see what the install messages are.
I think you should check bldeploy*log in Transaction/log dir and search for "Exit" string.
Probably you need to add such code: -2145124329,2359302 to Patch Global Configuration in Windows tab.
But where: success/failure/warning/reboot return codes it's your choice.
that doesn't seem to be the issue here. his bldeploy log does not show any errors during the patch deploy.