If you do this as a file deploy job as noted in the documentation you should see success, but ultimately you want to do a version check after running a USP job because sometimes the agent doesn't upgrade (usually more the case on windows and not unix).
Hi, I'm fairly new to the whole Bladelogic packaging.
I'm just creating my Automated Agent upgrade packages now.
I've read the Installation manual and understand how to do it, but if the job just finishes (because the installs are silent) how does one then check that they worked?
Would I need to create a second job that somehow checks the version of the agent (what exactly should I look for, the /usr/nsh/version file only has 7.6 no build/version number).
And then run this jobs against the same list of targets.
Oh and does the Agent install automatically exit if the existing agent on the target is the same or newer than the one being deployed or does it just overwrite the exisiting agent regardless?
We execute our silent install from an NSH script. That script contains a check to make sure the OS is the correct type and checks the /usr/nsh/version file to make sure the agent version needs to be upgraded. We run the silent install command and then issue a sleep command to give the installer time to upgrade and restart the agent. After the sleep command, the script checks the /usr/nsh/version file to make sure the upgrade was completed. I suppose you could also do an "agentinfo" command and parse the output for the agent version, which may be more accurate and confirm the agent was running correctly.
if the target agent is the same version as the current i believe it still 'upgrades', replacing whatever files an upgrade would replace (and preserve).
what you should do is create smart groups of server where RSCD_VERSION does not equal <new version> by os and platform.
then take your agent upgrade jobs, and target those smart groups accordingly.
I am out of the office from Wed 9/22 to Sun 9/26, and will not have access to voicemail or email during this time.