[CentOS] I broke "yum update" - C7

Thu Aug 29 16:26:27 UTC 2019
Gary Stainburn <gary.stainburn at ringways.co.uk>

On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote:
> rpm -Vv nss

[root at stan2 ~]# rpm -Vv nss
.........    /etc/pki/nss-legacy
.........  c /etc/pki/nss-legacy/nss-rhel7.config
.........    /etc/pki/nssdb
.........  c /etc/pki/nssdb/cert8.db
.........  c /etc/pki/nssdb/cert9.db
.........  c /etc/pki/nssdb/key3.db
.........  c /etc/pki/nssdb/key4.db
.........  c /etc/pki/nssdb/pkcs11.txt
.........  c /etc/pki/nssdb/secmod.db
.........    /usr/lib64/libnss3.so
.........  g /usr/lib64/libnssckbi.so
.........    /usr/lib64/libsmime3.so
.........    /usr/lib64/libssl3.so
.........    /usr/lib64/nss/libnssckbi.so
.........  d /usr/share/man/man5/cert8.db.5.gz
.........  d /usr/share/man/man5/cert9.db.5.gz
.........  d /usr/share/man/man5/key3.db.5.gz
.........  d /usr/share/man/man5/key4.db.5.gz
.........  d /usr/share/man/man5/pkcs11.txt.5.gz
.........  d /usr/share/man/man5/secmod.db.5.gz
[root at stan2 ~]# URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=epel update
[snip]
Loading mirror speeds from cached hostfile
2019-08-29 17:23:17,344 combined options: {
  'text'         : 'epel/x86_64/metalink',
  'delegate'     : {
    'async'        : None,
    'bandwidth'    : 0,
    'cache_openers': True,
    'checkfunc'    : None,
    'close_connection': 0,
    'copy_local'   : 0,
    'curl_obj'     : None,
    'data'         : None,
    'default_speed': 1000000.0,
    'delegate'     : None,
    'failfunc'     : <function _do_raise at 0x7fd3c45da848>,
    'failure_callback': None,
    'ftp_disable_epsv': False,
    'ftp_headers'  : None,
    'half_life'    : 2592000,
    'http_headers' : (),
    'interrupt_callback': None,
    'ip_resolve'   : None,
    'keepalive'    : True,
    'libproxy'     : False,
    'max_connections': 5,
    'max_header_size': 2097152,
    'minrate'      : 0,
    'mirror_group' : None,
    'multi_progress_obj': None,
    'no_cache'     : False,
    'opener'       : None,
    'password'     : None,
    'prefix'       : None,
    'progress_obj' : None,
    'proxies'      : None,
    'proxy'        : None,
    'quote'        : None,
    'range'        : None,
    'reget'        : None,
    'retry'        : 10,
    'retry_no_cache': False,
    'retrycodes'   : [-1, 2, 4, 5, 6, 7],
    'size'         : None,
    'ssl_ca_cert'  : None,
    'ssl_cert'     : None,
    'ssl_cert_type': 'PEM',
    'ssl_context'  : None,
    'ssl_key'      : None,
    'ssl_key_pass' : None,
    'ssl_key_type' : 'PEM',
    'ssl_verify_host': True,
    'ssl_verify_peer': True,
    'text'         : None,
    'throttle'     : 0,
    'timedhosts'   : None,
    'timeout'      : 30.0,
    'urlparser'    : <urlgrabber.grabber.URLParser instance at 0x7fd3bf6f3ab8>,
    'user_agent'   : 'urlgrabber/3.10 yum/3.4.3',
    'username'     : None,
    }
  }
2019-08-29 17:23:17,344 attempt 1/10: https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64
2019-08-29 17:23:17,345 opening local file "/var/cache/yum/x86_64/7/epel/metalink.xml.tmp" with mode wb
* About to connect() to mirrors.fedoraproject.org port 443 (#29)
*   Trying 8.43.85.67...
* Connected to mirrors.fedoraproject.org (8.43.85.67) port 443 (#29)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* Server certificate:
* 	subject: CN=*.fedoraproject.org,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
* 	start date: Feb 01 00:00:00 2017 GMT
* 	expire date: May 01 12:00:00 2020 GMT
* 	common name: *.fedoraproject.org
* 	issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
* NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER)
* Peer's Certificate issuer is not recognized.
* Closing connection 29
2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, 7], re-raising


 One of the configured repositories failed (Unknown),
 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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again