OPMS upgrade failure
search cancel

OPMS upgrade failure

book

Article ID: 137369

calendar_today

Updated On:

Products

CA App Synthetic Monitor

Issue/Introduction

When trying to upgrade the OPMS the installation failed with the following error:


===============================================================================

Installation Failed

-------------------

------


yes: standard output: Broken pipe

yes: write error



By looking at the yum logs (located at \opms\logs by default) we can see there are issues accessing the OS (eg: RHEL) repositories:


Loaded plugins: product-id, search-disabled-repos, subscription-manager

file:///mnt/hp/IBM/repositorio/current/rhel-7-server-extras-rpms/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/hp/IBM/repositorio/current/rhel-7-server-extras-rpms/repodata/repomd.xml"

Trying other mirror.


 One of the configured repositories failed (IBM Red Hat Enterprise Linux 7 Server - Extras (RPMs)),  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-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-server-extras-rpms

        or

            subscription-manager repos --disable=ibm-rhel-7-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-server-extras-rpms.skip_if_unavailable=true


failure: repodata/repomd.xml from ibm-rhel-7-server-extras-rpms: [Errno 256] No more mirrors to try.

file:///mnt/hp/IBM/repositorio/current/rhel-7-server-extras-rpms/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/hp/IBM/repositorio/current/rhel-7-server-extras-rpms/repodata/repomd.xml"


Environment

OPMS 10.2.1

Cause

This error indicates that the installation process cannot access the OS repositories (which is a prerequisite).

Resolution

By copying the repositories in the path where yum tries to locate the repositories allowed the installation to complete successfully.