When attempting a Centralized Agent Upgrade, the service manager fails to upgrade, and files are left behind. In review of the logs, you may see the following error:
chmod 755 <AE>/servicemanager/bin/ucybsmcl
ERROR 256: chmod 755 <AE>/servicemanager/bin/ucybsmgr
chmod: changing permissions of <AE>/servicemanager/bin/ucybsmgr: Operation not permitted
On AIX there may be an additional error in the Service Manager log, just after restart:
20200306/145337.905 - U00022063 Service Manager upgrade error: cannot remove file '%s'.
20200306/145337.905 - ERROR: errno '2' returned: No such file or directory
This can be caused if the Service Manager is ran under a non-root user and the Agent is ran as a root user; the files for the Centralized Agent Upgrade are written to the filesystem via root, but the chmod fails due to the lack of permissions on the user running the Service Manager
On AIX, even as root, there was an additional issue related to MLS.
Component: Agent for Unix and Service Manager
The workaround for this issue would be either
a.) upgrading the Agent and Service Manager manually
b.) running the Service Manager as the root user.
Update to a fix version listed below or a newer version if available.
Component(s): Agent Unix and ServiceManager
Automation.Engine 12.1.5 - Available
Automation.Engine 12.2.3 - Available
Automation.Engine 12.3.0 - Available
Problems with the Unix ServiceManager and the Unix Agent have been fixed where the upgrades triggered with a centralized agent upgrade sporadically fail or leave files behind.
The MLS issue on AIX is finally solved in:
Automation.Engine 12.2.6 - Available
Automation.Engine 12.3.3 - Planned release 2020-06-29