The pmgit unable to handle automatic git commit on servers with proxy configuration (4379257)

The pmgit unable to handle automatic git commit on servers with proxy configuration. However, manual operation works as intended.

The issue has been seen currently with remote GitHub and with the environment having proxies.

Example:

# cat /etc/environment

export http_proxy=http://proxy.prod.domain.com:8080
export https_proxy=http://proxy.prod.domain.com:8080
export HTTP_PROXY=http://proxy.prod.domain.com:8080
export HTTPS_PROXY=http://proxy.prod.domain.com:8080

The command pmgit update works fine if run manually; however, the automatic pmgit update or commit fails as pmgit binary can't handle the proxy variables.

There is no permanent solution for this issue right now however, the dev team has started to work on it to fix it in future releases.

The product defect- 489873 has been raised for this issue as well. 

The workaround for this issue:

The general idea is to push the settings into the call that pmloadcheck makes.

Move the binary slightly:

mv /opt/quest/sbin/pmgit /opt/quest/sbin/.pmgit.exec

Make a file /opt/quest/sbin/pmgit as a script ( chmod +x it ) that has:

#!/bin/sh

export http_proxy=http://proxy.prod.domain.com:8080
export https_proxy=http://proxy.prod.domain.com:8080
export HTTP_PROXY=http://proxy.prod.domain.com:8080
export HTTPS_PROXY=http://proxy.prod.domain.com:8080

exec /opt/quest/sbin/.pmgit.exec "$@"

Limitation:

The above works as a temporary fix. However, the issue with this is that pmgit, now .pmgit.exec, is a symlink. Every time the SFS is upgraded, this workaround will go away, and a redo is required.