After the upgrade, the VMware Aria Operations management pack for TCA stopped working.
search cancel

After the upgrade, the VMware Aria Operations management pack for TCA stopped working.

book

Article ID: 390022

calendar_today

Updated On: 03-26-2025

Products

VMware Aria Suite

Issue/Introduction

Whenever rebooting the cloud proxy nodes, user has to edit the file /etc/docker/daemon.json to restore certain configurations for the TCA management pack to function correctly after the reboot.

Specifically, you need to update the following setting: "insecure-registries": [#############.###.##########.###:8043"].

Now, when attempting to apply these updates after rebooting the CP nodes, you encounter the following error:

"Job for docker.service failed because the control process exited with error code."

See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
# systemctl status docker

× docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2025-03-04 15:05:12 UTC; 8min ago
   Duration: 1w 3h 42min 42.457s
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 715650 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 715650 (code=exited, status=1/FAILURE)
        CPU: 40ms

Mar 04 15:05:12 #############.###.##########.### systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Mar 04 15:05:12 #############.###.##########.### systemd[1]: Stopped Docker Application Container Engine.
Mar 04 15:05:12 #############.###.##########.### systemd[1]: docker.service: Start request repeated too quickly.
Mar 04 15:05:12 #############.###.##########.### systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 04 15:05:12 #############.###.##########.### systemd[1]: Failed to start Docker Application Container Engine.

Environment

VMware Aria Operations: 8.18.3

VMware Aria Operations Management Pack for TCA: 1.0.0

TCA: 3.1.1

TCP Bundle: 4.0

 

Cause

While updating the configuration file (daemon.json), a comma was unknowingly missed, which caused the VMware Aria Operations management pack for TCA to stop functioning and prevented configuration after the upgrade to VMware Aria Operations version 8.18.3.

Resolution

Update Cloud Proxy daemon.json file

  • Make sure to add the above REPO to the daemon.json on the Cloud Proxys a line for "insecure-registries".

    - Log into the Cloud Proxy via SSH as root
    - vi /etc/docker/daemon.json
    - Add the "insecure-registries" entry as shown below to all Cloud Proxies.


Example file:

{
"iptables": true,
"log-opts": {"max-size": "200m", "max-file": "1"},
"log-level": "info" ,
"live-restore": true,
"no-new-privileges": true,
"icc": false,
"insecure-registries" :[ "#############.###.##########.###:8043" ]
}