ASM - error installing OPMS 10.7 - Puppet failed to install one or more components - Code: 6

Products

• CA App Synthetic Monitor

Issue/Introduction

We are trying to install the new version of the OPMS on a new machine but we are getting error code 6. 
We have checked the configuration with other OPMS with the previous version and apparently they are configured the same

 

Environment

Release : 10.7

Component : APP SYNTHETIC MONITOR ENVIRONMENTAL

Cause

the puppet log file in /opt/asm/opms/logs contained errors like

 

2021-07-12 09:59:30 +0200 Puppet (err): Execution of '/usr/bin/yum -d 0 -e 0 -y install monit' returned 1: One of the configured repositories failed (IBM Red Hat Enterprise Linux 7.9 Server - Extras (RPMs) (HTTP)),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=ibm-rhel-7_9-server-extras-rpms ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable ibm-rhel-7_9-server-extras-rpms
        or
            subscription-manager repos --disable=ibm-rhel-7_9-server-extras-rpms

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=ibm-rhel-7_9-server-extras-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from ibm-rhel-7_9-server-extras-rpms: [Errno 256] No more mirrors to try.
http://server.domain.com/repos/RHEL/current_rhel7_9/rhel-7-server-extras-rpms/repodata/repomd.xml: [Errno 14] HTTP Error 504 - Gateway Timeout

Resolution

In this customer situation there was a security problem with the yum repositories which was corrected by the administrators