We tried to upgrade agents after applying patch 6.7.1 (6.7.0.b124) through the ROC. Even though the agent upgrade results indicated it was successful (without error), the agent still shows the agents previous version.
Some commands are needed to run the agent upgrade on linux machines via the ROC UI. The needed commands may not be available on the operating system where the agent is running. This usually indicates an older version of Linux that may not be officially supported by the agent anymore.
The recommended solution is based on the needed commands not being available. To see if this is the cause you can check for errors in the following file on the target agent machine:
If this file does not exist on the target agent machine then the problem, and possibly the solution, is different. Review the "Additional Information" section for more details on how the agent upgrade is handled when upgraded via the ROC.
Also, please review the system requirements page of the documentation for more details on which agent platforms are supported. It can be found here: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/intelligent-automation/release-automation-nolio/6-7/installation/system-requirements.html
Release : 6.7
Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER
Perform the agent upgrade via Automation Studio.
Automation Studio has been deprecated in version 6.7. But it is still available for a limited time by manually accessing the URL: http://nacserver:port/nolio-app/app.jsp
Agent Upgrades Via ROC:
Using the ROC to upgrade agents on Linux is done using a Nolio RA application with an artifact package. The process it runs:
The script writes its output to the log file: /tmp/.nolio-ra-agent/upgrade/agent-upgrade-bundle-linux-x86-64-unknown.zip/ra_process_entrypoint.log
If there is a problem and it is not creating an ra_process_entrypoint.log file then:
If there is a problem and it is creating an ra_process_entrypoint.log file then whatever problem the script had is likely logged in this file.
For example: On RHEL5/RHEL6 servers that don't have the realpath command you might see something like the following:
The first line shows the file/script where the realpath command is being called from. It's being used to provide an argument to the dirname command. Since the realpath command doesn't exist on this server it's not able to send the expected argument to the dirname command for it to successfully run.
Opening a Support Issue:
If you need to open a support issue relating to agent upgrades then the following information needs to be attached to the incident:
Minimum Info: for all issues
Additional Logs: for issues relating to the deployment of the agent upgrade artifact package.