VMware Tools Agent Installation Issue

I’m troubleshooting an agent installation using VMware Tools.  I deploy via Morpheus with the agent to install, in the logs I see the following:

I wait for it to finalize, which it never does.  I checked /var/log/messages and I see the following snippet:

Jun 28 10:57:42 proj2-customizations3 vmtoolsd: /bin/yum
Jun 28 10:57:42 proj2-customizations3 vmtoolsd: which: no dnf in (/sbin:/bin:/usr/sbin:/usr/bin)
Jun 28 10:57:42 proj2-customizations3 vmtoolsd: which: no apt-get in (/sbin:/bin:/usr/sbin:/usr/bin)
Jun 28 10:57:42 proj2-customizations3 vmtoolsd: which: no morpheus-node-ctl in (/sbin:/bin:/usr/sbin:/usr/bin)
Jun 28 10:57:43 proj2-customizations3 vmtoolsd: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
Jun 28 10:57:43 proj2-customizations3 vmtoolsd: : manager
Jun 28 10:57:43 proj2-customizations3 vmtoolsd: This system is not registered with an entitlement server. You can use subscription-manager to register.
Jun 28 10:57:43 proj2-customizations3 vmtoolsd: Cleaning repos: morpheus
Jun 28 10:57:43 proj2-customizations3 vmtoolsd: bash: line 81: /usr/bin/morpheus-node-ctl: No such file or directory
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: : manager
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: This system is not registered with an entitlement server. You can use subscription-manager to register.
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: Nothing to do
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: : manager
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: This system is not registered with an entitlement server. You can use subscription-manager to register.
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: Resolving Dependencies
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: --> Running transaction check
Jun 28 10:57:44 proj2-customizations3 vmtoolsd: ---> Package morpheus-vm-node.x86_64 0:3.2.7-1.el7 will be installed
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: --> Finished Dependency Resolution
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Dependencies Resolved
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: ================================================================================
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Package                 Arch          Version            Repository       Size
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: ================================================================================
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Installing:
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: morpheus-vm-node        x86_64        3.2.7-1.el7        morpheus        144 M
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Transaction Summary
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: ================================================================================
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Install  1 Package
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Total download size: 144 M
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Installed size: 0
Jun 28 10:57:46 proj2-customizations3 vmtoolsd: Downloading packages:
Jun 28 10:57:48 proj2-customizations3 vmtoolsd: Running transaction check
Jun 28 10:57:48 proj2-customizations3 vmtoolsd: Running transaction test
Jun 28 10:57:49 proj2-customizations3 vmtoolsd: Transaction test succeeded
Jun 28 10:57:49 proj2-customizations3 vmtoolsd: Running transaction
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: error: %pre(morpheus-vm-node-3.2.7-1.el7.x86_64) scriptlet failed, exit status 127
Jun 28 10:57:50 proj2-customizations3 yum[1695]: morpheus-vm-node-3.2.7-1.el7.x86_64: 100
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: Error in PREIN scriptlet in rpm package morpheus-vm-node-3.2.7-1.el7.x86_64
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: Verifying  : morpheus-vm-node-3.2.7-1.el7.x86_64
  1/1
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: Failed:
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: morpheus-vm-node.x86_64 0:3.2.7-1.el7
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: Complete!
Jun 28 10:57:50 proj2-customizations3 vmtoolsd: bash: line 88: /usr/bin/morpheus-node-ctl: No such file or directory
Jun 28 10:57:50 proj2-customizations3 systemd: Removed slice User Slice of root.
Jun 28 10:58:03 proj2-customizations3 chronyd[779]: Selected source 162.159.200.123
Jun 28 11:00:01 proj2-customizations3 systemd: Created slice User Slice of root.

I see it complain about /usr/bin/morpheus-node-ctl: No such file or directory but also about not being registered with an entitlement server.  However, if I run the downloaded and run the agent script manually on a deployed VM without the agent install attempted, it all works great, agent installs and starts communicating.  No registration or creation of that directory either.

Are these two different scripts or a way to test why it is failing with the VMware Tools?

It’s complaining about a problem with the PREIN script in the RPM, and since there’s an error, the agent RPM doesn’t fully get installed. What’s the OS?

Downloaded the latest from the site a bit ago.

so, just the raw iso?

Yea, used the DVD binaries and made a template from it. Basic install with the guest agents.

install cloud init

regardless your error implies to me something wrong with satellite registry maybe?

For the Satellite, I’m able to install manually with the script without making changes. Is it a different process to install the agent than the one downloaded via the UI?

There’s nothing in the pre script for an install that would cause an error

permission issue?

selinux?

I'm guessing it is running the upgrade portion, since I see the error /usr/bin/morpheus-ctl not existing, which probably comes from the stop command

thats in the install script

google tells me its user and group config and selinux

selinux is enabled but does not affect the after install. I do use the same user to install that I have on the virtual image.

I can try disabling selinux on the template and give that a shot, see if it gives a different result.

To close the loop, it was selinux.  I could reproduce the same issue if I tried to install the agent from the UI.  Created a new VM with no agent, disabled selinux, then tried to do the install via the UI and it worked.
 
Thanks for the triage!
whats
ls -l /etc/group
[korey@localhost ~]$ ls -l /etc/group

-rw-r–r–. 1 root root 600 Jun 28 10:19 /etc/group

yeah think selinux is preventing modding that, would need to dig in to it but think would need to set proper security context