Page Comparison

If you have installed Content Gateway on version 7.9-7.10 when offline (the gateway can’t reach the internet), it is possible that you do not have the swarmlifecycle script running correctly on your system. This can also happen on RHEL 8 or 9 (and variants) if pip3 was not available when Content Gateway was installed.

...

1. Download https://support.cloud.datacore.com/tools/datacore-swarmlifecycle-dependencies.tgz

2. Transfer this tarball to your gateway(s).

3. SSH to the gateway and unpack the tarball with tar zxvf [filename]

4. The script should now be in a tmp subdirectory from where you unpacked it.

5. Run: cd tmp to move to that directory.

6. Verify the pip3 command is available. If not, run yum install -y python3-pip.

7. Run: pip3 install *whl to install the dependencies.

8. Run: pip3 install /opt/caringo/cloudgateway/bin/datacore-swarmlifecycle.tar.gz to update to the latest version of the swarmlifecycle script provided by the most recent gateway installation.

9. Verify the script is installed by running: /usr/local/bin/swarmlifecycle --version

See also

...

https://caringo.atlassian.net/wiki/spaces/public/pages/2931753040/Enforcement#Policy-Action