Failed to synchronize cache for repo 'rhel-8-for-x86_64-baseos-beta-rpms', ignoring this repo

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux (RHEL) 8 Beta

Issue

  • When trying to access the Content Delivery Network (CDN) Channels trough a squid proxy, the following errors are shown:

    Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-beta-rpms', ignoring this repo.
    Failed to synchronize cache for repo 'rhel-8-for-x86_64-baseos-beta-rpms', ignoring this repo.
    

Resolution

  • Red Hat is aware of this issue and is planning to resolve this in an upcoming version of RHEL.
  • Please open a support case at Red Hat if this issue is impacting your environment.

Diagnostic Steps

Steps to reproduce the problem:

  1. Add your proxy server and your proxy port to the /etc/rhsm/rhsm.conf file by issuing the following command:

    # subscription-manager config --server.proxy_hostname=squid.corp.redhat.com --server.proxy_port=3128
    
  2. Run the command:

    # dnf repolist
    Updating Subscription Management repositories.
    Updating Subscription Management repositories.
    Red Hat Enterprise Linux 8 for x86_64 - AppStream HTB (RPMs)          0.0  B/s |   0  B     00:01    
    Red Hat Enterprise Linux 8 for x86_64 - BaseOS HTB (RPMs)             0.0  B/s |   0  B     00:01    
    Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-htb-rpms', ignoring this repo.
    Failed to synchronize cache for repo 'rhel-8-for-x86_64-baseos-htb-rpms', ignoring this repo.
    

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

5 Comments

I am having the same problem and not using a proxy server that I am aware of. Noticed 2 days ago that I thought I saw a package and later searching with yum it wasn't there anymore. Didn't think I needed it at the time, so didn't think much of it. Then I uninstalled, then re-installed samba server packages (because I needed the distribution's config files again) but there was no record of a samba package using yum search commands.

~~~Also, the command~~~~~

dnf repolist

~~~Outputs~~~~~~~~~~~~~~

Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-beta-rpms', ignoring this repo. Failed to synchronize cache for repo 'rhel-8-for-x86_64-baseos-beta-rpms', ignoring this repo.

~~~~~~~~~~~~~~~

I think those are the two primary software repositories, so I think I can't install any more packages?

~~~~Also I tried~~~~~~

sudo yum makecache

~~~~~~~~~

With no solution to problem either.

Also sorry about posting same thing twice. This is newbie's first time. If someone can delete one of them, would make me feel better.

I think I answered my own question. All good things come to an end right? I think Red Hat Linux 8 is out now. So Beta is discontinued? I am assuming something like that.

I am having the same problem and not using a proxy server that I am aware of. Noticed 2 days ago that I thought I saw a package and later searching with yum it wasn't there anymore. Didn't think I needed it at the time, so didn't think much of it. Then I uninstalled, then re-installed samba server packages (because I needed the distribution's config files again) but there was no record of a samba package using yum search commands.

~~~Also, the command~~~~~ dnf repolist ~~~Outputs~~~~~~~~~~~~~~ Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-beta-rpms', ignoring this repo.

Failed to synchronize cache for repo 'rhel-8-for-x86_64-baseos-beta-rpms', ignoring this repo. ~~~~~~~~~~~~~~~ I think those are the two primary software repositories, so I think I can't install any more packages?

~~~~Also I tried~~~~~~ sudo yum makecache ~~~~~~~~~ With no solution to problem either.

OpenStack Stein Repository 58 B/s | 38 B 00:00 Error: Failed to synchronize cache for repo 'openstack-stein'

How to resolve this one