# RPM repositories broken?

**URL:** <https://community.netdata.cloud/t/rpm-repositories-broken/3669>\
**Category:** Help\
**Created:** [December 22, 2022, 4:47pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669 "2022-12-22T16:47:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![twk](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/twk/32/2482_2.png) [@twk](https://community.netdata.cloud/u/twk)\
**Post date:** [December 22, 2022, 4:47pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669/1 "2022-12-22T16:47:57Z")

</div>

We noticed our yum updates failed today:

```auto
https://repo.netdata.cloud/repos/edge/el/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

```

Here’s our repo config:

```auto
[netdata-edge]
name=Netdata Edge
baseurl=https://repo.netdata.cloud/repos/edge/el/$releasever/$basearch
repo_gpgcheck=1
gpgcheck=1
gpgkey=https://repo.netdata.cloud/netdatabot.gpg.key
enabled=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
priority=50

[netdata-repoconfig]
name=Netdata Repository Config
baseurl=https://repo.netdata.cloud/repos/repoconfig/el/$releasever/$basearch
repo_gpgcheck=1
gpgcheck=1
gpgkey=https://repo.netdata.cloud/netdatabot.gpg.key
enabled=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
priority=50

```

Did someone change the $releasever path from 7Server to 7 on the repo hosting side?

```auto
# curl -Is https://repo.netdata.cloud/repos/edge/el/7/x86_64/repodata/repomd.xml | head -n 1
HTTP/1.1 200 OK

```

Thank you.

---

<div class="post-metadata">

**Author:** ![Austin\_Hemmelgarn](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/austin_hemmelgarn/32/4495_2.png) [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)\
**Post date:** [December 22, 2022, 6:01pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669/2 "2022-12-22T18:01:11Z")

</div>

We’ve just recently switched to new hosting infrastructure for our RPM repositories, and this appears to be a result of a quirk of RHEL that we were not aware of when setting up the infrastructure originally (none of CentOS, Alma Linux, or Rocky Linux appear to behave this way, and we don’t have RHEL systems available for testing).

We’re working on getting this fixed, and it should be working correctly within the next hour or so.

---

<div class="post-metadata">

**Author:** ![twk](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/twk/32/2482_2.png) [@twk](https://community.netdata.cloud/u/twk)\
**Post date:** [December 22, 2022, 6:16pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669/3 "2022-12-22T18:16:37Z")

</div>

I appreciate the quick response. Please let me know if you need any additional info.

---

<div class="post-metadata">

**Author:** ![Austin\_Hemmelgarn](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/austin_hemmelgarn/32/4495_2.png) [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)\
**Post date:** [December 22, 2022, 6:21pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669/4 "2022-12-22T18:21:53Z")

</div>

Things are fixed now on the backend server (we’ve added symlinks so that these particular values for `$releasever` get properly redirected just like the old infrastructure apparently did), and we’ve told CloudFlare to purge any negative cache entries for those paths, so things _should_ be working correctly now.

---

<div class="post-metadata">

**Author:** ![twk](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/twk/32/2482_2.png) [@twk](https://community.netdata.cloud/u/twk)\
**Post date:** [December 22, 2022, 6:21pm UTC](https://community.netdata.cloud/t/rpm-repositories-broken/3669/5 "2022-12-22T18:21:56Z")

</div>

It’s looking good now. Thank you!