Cengn build failure due to epel.blizoo.mk

[Scott Little]

Brief Description
-----------------
Cengn builds periodically fail when an upstream rpm repo in anavailable. By far the top offender is epel.blizoo.mk that seems to go offline roughly monthly.

The only rpm that we currently use from that repo is python-pyngus-2.2.1-1.el7.noarch.rpm, referenced from rpms_centos3rdparties.lst.

However that rpm is eclipsed by the newer python2-pyngus-2.2.4-1.el7.noarch.rpm which we reference from rpms_centos.lst.

It is python2-pyngus-2.2.4-1.el7.noarch.rpm that is used in our ISO build. I suspect it is true for our docker images as well.

If verified, please remove python-pyngus-2.2.1-1.el7.noarch.rpm from rpms_centos3rdparties.lst, and then remove the repo 'yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo' as it will no longer be supplying rpms that are both unique and needed.

Severity
--------
Major

Steps to Reproduce
------------------
cd stx-tools
docker build --tag stx-builder --file ../Dockerfile .

Expected Behavior
------------------
Creation of a docker image called stx-builder

Actual Behavior
----------------
docker build command failes

Reproducibility
---------------
aprox once per month

System Configuration
--------------------
N/A

Branch/Pull Time/Commit
-----------------------
2019-05-30 01:30:00 utc

Last Pass
---------
2019-04-28

Timestamp/Logs
--------------
http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: epel.blizoo.mk; Unknown error"
Trying other mirror.


 One of the configured repositories failed (Starlingx-epel.blizoo.mk_epel_7Server_x86_64 - epel.blizoo.mk_epel_7Server_x86_64),
 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=Starlingx-epel.blizoo.mk_epel_7Server_x86_64 ...

     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 Starlingx-epel.blizoo.mk_epel_7Server_x86_64
        or
            subscription-manager repos --disable=Starlingx-epel.blizoo.mk_epel_7Server_x86_64

     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=Starlingx-epel.blizoo.mk_epel_7Server_x86_64.skip_if_unavailable=true

failure: repodata/repomd.xml from Starlingx-epel.blizoo.mk_epel_7Server_x86_64: [Errno 256] No more mirrors to try.
http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: epel.blizoo.mk; Unknown error"

Test Activity
-------------
Build

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/662467

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/662467
Committed: https://git.openstack.org/cgit/starlingx/tools/commit/?id=78258f737f68f4ff8cfcc226acdcc9654a979e51
Submitter: Zuul
Branch: master

commit 78258f737f68f4ff8cfcc226acdcc9654a979e51
Author: Scott Little <email address hidden>
Date: Thu May 30 11:58:49 2019 -0400

    remove repo blizoo.mk

    Cengn builds periodically fail when an upstream rpm repo in anavailable.
    By far the top offender is epel.blizoo.mk that seems to go offline
    roughly monthly.

    The only rpm that we currently use from that repo is
    python-pyngus-2.2.1-1.el7.noarch.rpm, referenced from
    rpms_centos3rdparties.lst.

    However that rpm is eclipsed by the newer
    python2-pyngus-2.2.4-1.el7.noarch.rpm which we reference from
    rpms_centos.lst.

    It is python2-pyngus-2.2.4-1.el7.noarch.rpm that is used in our ISO
    build. Pyngus is not used in our docker images.

    This update will remove python-pyngus-2.2.1-1.el7.noarch.rpm
    from rpms_centos3rdparties.lst, and remove the repo ...
    'yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo' as it will
    no longer be supplying rpms that are both unique and needed.

    Testing:
    docker build --tag stx-builder --file Dockerfile .
    build-pkgs
    build-iso
    build-stx-base
    build-stx-images

    Change-Id: I817dae97282474a0c9b56941e4b227b6ff82d9aa
    Closes-Bug: 1831113
    Signed-off-by: Scott Little <email address hidden>

[Ghada Khalil (gkhalil)]

Marking as stx.2.0 release gating - build issue