# RPM Repo Broken with RHEL Satellite

**URL:** <https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359>\
**Category:** Elasticsearch\
**Created:** [July 27, 2015, 6:09pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359 "2015-07-27T18:09:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [July 27, 2015, 6:09pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/1 "2015-07-27T18:09:54Z")

</div>

I was trying to add the RPM repo's provide by Elastic to my RHEL Satelite 6.0 server as that is how we do patch management. I was

I opened a case with Redhat to make sure of the issue is with Our environment or the repo. This is what they came back with.

CASE 01478075

```
Hello,

As per below bugzilla Indexing should be enabled on Webserver,

https://bugzilla.redhat.com/show_bug.cgi?id=1202826

Would you please check this with maintainer of website to know this has enabled already ?

Kind Regards,
Amit Upadhye.
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 27, 2015, 10:15pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/2 "2015-07-27T22:15:31Z")

</div>

I've asked one of the infra team to comment.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 27, 2015, 10:28pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/3 "2015-07-27T22:28:21Z")

</div>

We've now got an internal task to enable this for you and any others that may want to use this method 🙂

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [July 28, 2015, 2:07pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/4 "2015-07-28T14:07:04Z")

</div>

Awesome! Thanks! It will make it so much easier.

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [August 2, 2015, 3:33pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/5 "2015-08-02T15:33:59Z")

</div>

I don't mean to pester, but do the admins have a time frame when they will get to it. I will be deploying +100 servers with Logstash and rather push it remotely then have to login to every server to do the yum add.

I do have alternatives but if I could do it the first time the right way, saves me from testing it later on.

Thanks,

Ed

---

<div class="post-metadata">

**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\
**Post date:** [February 15, 2016, 4:49pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/6 "2016-02-15T16:49:00Z")

</div>

Ed, thanks so much for your patience on this one. The issue is that our artifacts are not stored next to a traditional web server where we can simply flip on `+Indexes`. We store the artifacts on S3, then for good measure throw a proxy on top so that we can provide nice things like redirects and metrics to improve the experience for all (except in this case!).

We've been working to solve a bigger issue to make our software repository more robust, but I think we can probably do something here as a stopgap. I created this by hand based on a Debian mirror's `index.html`:

[https://download.elastic.co/logstash/logstash/index.html](https://download.elastic.co/logstash/logstash/index.html)

Can you tell us if this would satisfy RHEL Satellite Server's requirements? That way we could simply populate these in every "directory" on S3 and hopefully help everyone.

Thanks!

Drew

---

<div class="post-metadata">

**Author:** ![drewr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewr/32/7803_2.png) [@drewr](https://discuss.elastic.co/u/drewr)\
**Post date:** [February 15, 2016, 4:52pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/7 "2016-02-15T16:52:43Z")

</div>

I guess for a more realistic test you'd need something that linked to RPMs. Try this one.

[https://download.elasticsearch.org/logstash/logstash/packages/centos/index.html](https://download.elasticsearch.org/logstash/logstash/packages/centos/index.html)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:16pm UTC](https://discuss.elastic.co/t/rpm-repo-broken-with-rhel-satellite/26359/8 "2017-07-05T23:16:20Z")

</div>


