# Missing repodata/filelists.xml in yum repo causes repo sync to fail **URL:** \ **Category:** Elasticsearch\ **Created:** [February 6, 2025, 9:04am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168 "2025-02-06T09:04:53Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![sobjerke](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sobjerke](https://discuss.elastic.co/u/sobjerke)\ **Post date:** [February 6, 2025, 9:04am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/1 "2025-02-06T09:04:53Z")
We are using Red Hat Satellite server to distribute rpm packages to our servers. It synchronizes the Elasticsearch 8.x yum repository ([https://artifacts.elastic.co/packages/8.x/yum](https://artifacts.elastic.co/packages/8.x/yum)) only downloading repository metadata and the packages we actually use (download policy "On demand"). Since late January, synchronizing the repository has failed due to the upstream repository metadate missing the file repodata/filelists.xml. Also repodata/repomd.xml should have a reference to this file. There must have been some change to the metadata generation lately since we had this working earlier in January. Would it be possible to generate the complete metadata again? ---
**Author:** ![reiold](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@reiold](https://discuss.elastic.co/u/reiold)\ **Post date:** [February 7, 2025, 6:30am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/2 "2025-02-07T06:30:07Z")
We have the same problem with RH Satellite 6.15.5.2 at RPM Repo Sync " **Errors:** XML file(s): filelists not found" ---
**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\ **Post date:** [February 7, 2025, 6:46am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/3 "2025-02-07T06:46:26Z")
We had an incident related to RPM packages earlier this week, but it should be resolved now: [ESS (Public) Status - Ubuntu/Debian and Fedora package repositories disruption](https://status.elastic.co/incidents/505tp7pf0stw). Indeed, I was able to follow [Install Elasticsearch with RPM | Elasticsearch Guide [8.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html) on a Fedora Docker image: ```auto $ docker run -ti fedora:latest bash [root@90368c78fb2d /]# cat > /etc/yum.repos.d/elasticsearch.repo [elasticsearch] name=Elasticsearch repository for 8.x packages baseurl=https://artifacts.elastic.co/packages/8.x/yum gpgcheck=1 gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch enabled=0 autorefresh=1 type=rpm-md [root@90368c78fb2d /]# sudo dnf install --enablerepo=elasticsearch elasticsearch Updating and loading repositories [...] [1/3] Verify package files [2/3] Prepare transaction [3/3] Installing elasticsearch-0:8.17.1-1.aarch64 Complete! ``` ---
**Author:** ![reiold](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@reiold](https://discuss.elastic.co/u/reiold)\ **Post date:** [February 7, 2025, 7:20am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/4 "2025-02-07T07:20:44Z")
Hi, we use the Upstream URL: [https://artifacts.elastic.co/packages/8.x/yum](https://artifacts.elastic.co/packages/8.x/yum) We got still " **Errors:** XML file(s): filelists not found" on Upstream Sync, Installtion with attached direct attached Repo works, Upstream sync not! Thanks. ---
**Author:** ![sobjerke](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sobjerke](https://discuss.elastic.co/u/sobjerke)\ **Post date:** [February 7, 2025, 7:28am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/5 "2025-02-07T07:28:34Z")
The issue reported in this thread has not been resolved. I have verifed that today. Yes, you can install rpms from the repo if you add the repo directly to a host, but the point of using satellite server to distribute software, is to get the same version installed on all our hosts. Satellite is unable to use the repository with the current metadata. ```auto $ wget -q https://artifacts.elastic.co/packages/8.x/yum/repodata/repomd.xml $ grep 'data type=' repomd.xml ``` We are missing \ here. We have tried downloading the entire repository manually (outside satellite) and rebuild the metadata ourselves (using createrepo), and then we get: ```auto ``` This method is however impractical as we need to do a complete download of all rpms instead of just the metadata and the rpms we need. It will also cause more load on the upstream servers, in pareticular if a lot of satellite users starts using this method to overcome the issue. ---
**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\ **Post date:** [February 7, 2025, 10:58am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/6 "2025-02-07T10:58:39Z")
Created a topic as well before I saw this one. This was my post (will delete the other thread): Since recently the repository of version 8 cannot be reached from RedHat Satellite (issues reported with 6.11, 6.15 and 6.16). This is already mentioned in this topic: [Apt repo change? "E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Origin' value from 'elastic' to 'Artifactory'" - #16 by Tuckson](https://discuss.elastic.co/t/apt-repo-change-e-repository-https-artifacts-elastic-co-packages-8-x-apt-stable-inrelease-changed-its-origin-value-from-elastic-to-artifactory/374021/16) but since the original question of this topic was solved, and no more reactions were given, I thought it better to open a new topic. Multiple users reported this issue. RedHat Satellite is widely known with companies as the primairy way to maintain and provision their RedHat systems. It currently is on version 6.16 which is not to be confused with rhel6 . My Satellite 6.16.runs on rhel9 . # Other users reported in the topic mentioned above: [sobjerke](https://discuss.elastic.co/u/sobjerke)[Svein Olav Bjerkeset](https://discuss.elastic.co/u/sobjerke) [2d](https://discuss.elastic.co/t/apt-repo-change-e-repository-https-artifacts-elastic-co-packages-8-x-apt-stable-inrelease-changed-its-origin-value-from-elastic-to-artifactory/374021/17) It seems to still be a problem with the upstream repositories. We have the same issue from Satellite 6.15 on RHEL8 and Satellite 6.16 on RHEL9. The following URLs all return 404 (Not Found): [https://artifacts.elastic.co/packages/8.x/yum](https://artifacts.elastic.co/packages/8.x/yum) [https://artifacts.elastic.co/packages/oss-8.x/yum](https://artifacts.elastic.co/packages/oss-8.x/yum) [https://artifacts.elastic.co/packages/8.x/apt](https://artifacts.elastic.co/packages/8.x/apt) Testing the URLs with cURL gives the same 404 error code. [mkadlics](https://discuss.elastic.co/u/mkadlics) [2d](https://discuss.elastic.co/t/apt-repo-change-e-repository-https-artifacts-elastic-co-packages-8-x-apt-stable-inrelease-changed-its-origin-value-from-elastic-to-artifactory/374021/19) Similar issue with salt/saltstack was solved by enabling the "Enable File List Indexing" option on the upstream Artifactory rpm repo: [Unable to create local mirror of saltstack repo, due to filelists.xml not being available · Issue #67032 · saltstack/salt · GitHub](https://github.com/saltstack/salt/issues/67032) Not sure if it is the issue here, but seems to be very similar. [ sobjerke](https://discuss.elastic.co/u/sobjerke)[Svein Olav Bjerkeset](https://discuss.elastic.co/u/sobjerke) [2d](https://discuss.elastic.co/t/apt-repo-change-e-repository-https-artifacts-elastic-co-packages-8-x-apt-stable-inrelease-changed-its-origin-value-from-elastic-to-artifactory/374021/20) The following URL works via cURL: [https://artifacts.elastic.co/packages/8.x/yum/repodata/repomd.xml](https://artifacts.elastic.co/packages/8.x/yum/repodata/repomd.xml) But: The repomd.xml file has no entry for data type="filelists" which seems to be expected by Red Hat Satellite server. [sobjerke](https://discuss.elastic.co/u/sobjerke)[Svein Olav Bjerkeset](https://discuss.elastic.co/u/sobjerke) [2d](https://discuss.elastic.co/t/apt-repo-change-e-repository-https-artifacts-elastic-co-packages-8-x-apt-stable-inrelease-changed-its-origin-value-from-elastic-to-artifactory/374021/21) Also note that we have had the 8.x yum repo working with Satellite 6.16 until a week or two ago, so there must have been some changes to the upstream repository that causes the repository sync to fail now. =========================== Please fix this since it blocks us from installing and upgrading on our systems. Also note that I found no problems with the version 7 repo. ---
**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\ **Post date:** [February 7, 2025, 1:28pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/7 "2025-02-07T13:28:21Z")
As we continue to look into this internally, can I please ask if this is an option for you? > **[How to forcefully regenerate metadata of a content view or repository on Red...](https://access.redhat.com/solutions/3396941)** > > How to recreate metadata of a Content View or Repository? Unable to update package(s) and the below error is faced:... ---
**Author:** ![atorok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atorok/32/83740_2.png) [@atorok](https://discuss.elastic.co/u/atorok)\ **Post date:** [February 7, 2025, 1:34pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/8 "2025-02-07T13:34:08Z")
We did indeed roll out a change that stopped providing filelist.xml as a result. While this is something that we have indeed provided in the past, it makes metadata operations slower and is not required for the elastic packaging repositories to function correctly. Our tests pass on all OSes from our support matrix. Can you help me understand if there is no way to configure a repo in Red Hat Satellite without a filelist ? Is this metadata that Satellite can be configured to create on it's own if your setup requires it for some reason ? ---
**Author:** ![sobjerke](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sobjerke](https://discuss.elastic.co/u/sobjerke)\ **Post date:** [February 7, 2025, 1:57pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/9 "2025-02-07T13:57:35Z")
"Republish Repository Metadata" for the ES 8.x repo did not resolve the issue. We still got the same error. Even if it had worked, it would mean we would have to republish before each sync, which would not be practical. I can see no option in the repository configuration in Satellite which would let us sync it without filelists.xml. I can open a support case with Red Hat and ask to make sure. ---
**Author:** ![atorok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atorok/32/83740_2.png) [@atorok](https://discuss.elastic.co/u/atorok)\ **Post date:** [February 7, 2025, 3:21pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/10 "2025-02-07T15:21:16Z")
It would be great if you could reach out to Red Hat! Thank you! We're open to the idea of addings this metadata back if there's no way at all for Satellite to work without it. I find it strange that the this is the case, but I'm not familiar with this product. I'll keep monitoring this thread. ---
**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\ **Post date:** [February 7, 2025, 3:24pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/11 "2025-02-07T15:24:04Z")
I strongly suggest you gain some experience on the way Satellite behaviors (you as in Elastic, not you as in atorok per sé 😉 ) . As I stated above, It is widely used in larger environments to manage patching processes on corporate RedHat landscapes. ---
**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\ **Post date:** [February 7, 2025, 3:42pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/12 "2025-02-07T15:42:11Z")
Satellite hosts repositories itself. Forcefully regenerate metadata is about it's own repositories, not about the upstream package sources. There simply seems to be no option other than creating a local mirror of Elastic's repository structure, then generate the file, and use that as upstream repo for satellite. Not only this seems unlogical, it also beats the purpose of having Satellite being the one-stop-shop on our enviroment for managing package streams from the internet and to our servers. ---
**Author:** ![Xiaohui](https://avatars.discourse-cdn.com/v4/letter/x/839c29/32.png) [@Xiaohui](https://discuss.elastic.co/u/Xiaohui)\ **Post date:** [February 9, 2025, 3:30pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/13 "2025-02-09T15:30:31Z")
It looks like the `yum makecache` command requires the `filelist.xml.gz` file. I was able to reproduce the error on an Amazon Linux 2 OS and centos 7. However, running `yum makecache fast` will work. 1. Start up a VM on AWS with Amazon Linux 2 OS. 2. Follow steps in [this guide](https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html#_yum) to add `/etc/yum.repos.d/elastic.repo`. 3. Run `yum makecache` command to trigger the error. ```auto [ec2-user@ip-172-31-29-120 ~]$ uname -a Linux ip-172-31-29-120.ec2.internal 5.10.233-224.894.amzn2.x86_64 #1 SMP Mon Jan 27 16:52:48 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux [ec2-user@ip-172-31-29-120 ~]$ sudo rm -rf /var/cache/yum [ec2-user@ip-172-31-29-120 ~]$ sudo yum makecache Loaded plugins: extras_suggestions, langpacks, priorities, update-motd amzn2-core | 3.6 kB 00:00:00 amzn2extra-docker | 2.9 kB 00:00:00 amzn2extra-kernel-5.10 | 3.0 kB 00:00:00 elastic-8.x | 1.1 kB 00:00:00 (1/15): amzn2-core/2/x86_64/group_gz | 2.7 kB 00:00:00 (2/15): amzn2-core/2/x86_64/updateinfo | 1.0 MB 00:00:00 (3/15): amzn2-core/2/x86_64/filelists_db | 66 MB 00:00:01 (4/15): amzn2extra-docker/2/x86_64/filelists_db | 41 kB 00:00:00 (5/15): amzn2extra-docker/2/x86_64/updateinfo | 22 kB 00:00:00 (6/15): amzn2extra-docker/2/x86_64/primary_db | 119 kB 00:00:00 (7/15): amzn2extra-docker/2/x86_64/other_db | 39 kB 00:00:00 (8/15): amzn2extra-kernel-5.10/2/x86_64/updateinfo | 104 kB 00:00:00 (9/15): amzn2-core/2/x86_64/other_db | 24 MB 00:00:01 (10/15): amzn2extra-kernel-5.10/2/x86_64/filelists_db | 18 MB 00:00:00 (11/15): amzn2-core/2/x86_64/primary_db | 74 MB 00:00:02 (12/15): amzn2extra-kernel-5.10/2/x86_64/primary_db | 33 MB 00:00:01 (13/15): amzn2extra-kernel-5.10/2/x86_64/other_db | 13 MB 00:00:00 (14/15): elastic-8.x/primary | 682 kB 00:00:00 (15/15): elastic-8.x/other | 51 kB 00:00:00 elastic-8.x 1674/1674 Error: requested datatype filelists not available ``` but `yum makecache fast` works fine. ```auto [ec2-user@ip-172-31-29-120 ~]$ sudo yum makecache fast Loaded plugins: extras_suggestions, langpacks, priorities, update-motd amzn2-core | 3.6 kB 00:00:00 amzn2extra-docker | 2.9 kB 00:00:00 amzn2extra-kernel-5.10 | 3.0 kB 00:00:00 elastic-8.x | 1.1 kB 00:00:00 Metadata Cache Created ``` and, yum intall/update commands are all running fine. ---
**Author:** ![atorok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atorok/32/83740_2.png) [@atorok](https://discuss.elastic.co/u/atorok)\ **Post date:** [February 10, 2025, 7:04am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/14 "2025-02-10T07:04:05Z")
The conclusion we reached is that while packages are installable just fine, `yum makecache` specifically fails on some older but still supported OSes and there doesn't seem to be a configuration option to make yum work without it. We're looking for solutions. ---
**Author:** ![sobjerke](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sobjerke](https://discuss.elastic.co/u/sobjerke)\ **Post date:** [February 10, 2025, 8:02am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/15 "2025-02-10T08:02:51Z")
I got this from Red Hat support regarding the use of filelists.xml in the latest version of Satellite server (6.16): > Satellite, as it's designed today, would not be able to sync any repos missing filelists or other.xml files from their repodata. If you want to do it today, You will have to locally mirror that repo somewhere, if needed on /pub of satellite, generate a metadata of that local mirror and then sync it in satellite. ---
**Author:** ![marrc.rousseau](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@marrc.rousseau](https://discuss.elastic.co/u/marrc.rousseau)\ **Post date:** [February 10, 2025, 9:00am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/16 "2025-02-10T09:00:00Z")
@atorok Same issue here. Please could you add this metadata back as it's needed by Satellite. Thanks ---
**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\ **Post date:** [February 10, 2025, 9:33am UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/17 "2025-02-10T09:33:25Z")
Rhel 9.5 is definately not 'older'. This issue has nothing to do with the OS, but is related to the product "RedHat Satellite" [Red Hat Satellite](https://www.redhat.com/en/technologies/management/satellite) . ---
**Author:** ![A.Klos](https://avatars.discourse-cdn.com/v4/letter/a/977dab/32.png) [@A.Klos](https://discuss.elastic.co/u/A.Klos)\ **Post date:** [February 10, 2025, 12:07pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/18 "2025-02-10T12:07:07Z")
same issue here .. we also need a solution to get it work .. will open a support case. ---
**Author:** ![A.Klos](https://avatars.discourse-cdn.com/v4/letter/a/977dab/32.png) [@A.Klos](https://discuss.elastic.co/u/A.Klos)\ **Post date:** [February 10, 2025, 12:27pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/19 "2025-02-10T12:27:26Z")
You wrote: > [@atorok](#): > > We did indeed roll out a change that stopped providing filelist.xml as a result. While this is something that we have indeed provided in the past, it makes metadata operations slower and is not required for the elastic packaging repositories to function correctly. Our tests pass on all OSes from our support matrix. it seems your test did't passed software deployment tools like redhat satellite? ---
**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\ **Post date:** [February 10, 2025, 12:30pm UTC](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168/20 "2025-02-10T12:30:03Z")
solution is simple. Nightly crontab with /bin/createrepo\_c [patch to artifactory yum directory on disk that contains elastic-8x] This generates the necessary XML files again. [Next page](https://discuss.elastic.co/t/missing-repodata-filelists-xml-in-yum-repo-causes-repo-sync-to-fail/374168.md?page=2)