have you checked "Transactions" logs? looks like issue is with file system size. Please check Transactions log messages.
Thanks for response.
Issue has been resolved after create agent bundle and execute on target through agent installer job.
But, after successfully upgrade agent, i'm getting a warning in job log for Pending Reboot.
Info Successfully installed/upgraded the Agent to version '22.214.171.1244'
Info Updating configuration objects registration.
Info Updating all server properties.
Info --- End of Upgrade Logs ---
Info Product: BMC Server Automation RSCD Agent -- Installation completed successfully.
Info Not running on a domain controller.
Info Added dependencies: lanmanserver to RSCDsvc.
Info BMC Server Automation RSCD Agent service started successfully.
Info Agent service removed successfully.
Info RSCD Agent service stopped successfully.
Info Firewall enabled.
Info DAALRegistry.xml does not need to be modified
Warning Windows Installer has detected a pending reboot request.
Info --- Upgrade Logs ---
Info The agent on server 10.8.62.155 is successfully up and running.
Info Attempt number 2 to validate that the agent on server 10.8.62.155 is up and running.
That is a warning message based on "reboot options" setting from "job options" in your job.
How can we avoid it?
And is there any issue on target machine due to this warning?
no issue. Just you can select "ignore" option from your job.
first of all - you shouldn't be using a deploy job to upgrade the agent. so it looks like you resolved that. what options did you pass to the MSI for the depot software of the rscd installer ? there's a couple to ignore the reboot state.
msiexec /I "??SOURCE??" /qn ALLUSERS=1 REBOOT=ReallySuppress PENDINGREBOOTFORCE=1
Is there any way to differentiate a pending reboot request from an unrelated MSI install from e.g. a failed or partially completed Bladelogic MSI install? If the pending reboot request is there for a reason couldn't it cause issues to re-run the installer with the pendingrebootforce option?
I believe if the rscd needs a reboot it will exit w/ a 3010 exit code.
also - it's not an error - it's a warning. i believe it's just checking the pendingfilerenameoperations key and there was probably reboot set for something else.