# RPM Distributions delayed again?

**URL:** <https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994>\
**Category:** Build\
**Tags:** releases, discuss\
**Created:** [September 12, 2021, 3:11pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994 "2021-09-12T15:11:41Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [April 4, 2022, 8:18pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/21 "2022-04-04T20:18:41Z")

</div>

Here’s the updated status:

We are still reviewing the below PR’s and making changes based on the review comments,

[https://github.com/opensearch-project/opensearch-build/pull/1807](https://github.com/opensearch-project/opensearch-build/pull/1807)  
[https://github.com/opensearch-project/opensearch-build/issues/1545](https://github.com/opensearch-project/opensearch-build/issues/1545)

**Merged the below PR’s**

We fixed issues to have the Centos7 OpenSearch Dashboards runner to correctly export fpm and also to allow dynamic node version switch

[https://github.com/opensearch-project/opensearch-build/pull/1888](https://github.com/opensearch-project/opensearch-build/pull/1888)

Add dashboards rpm assemble support in opensearch-build repo  
[https://github.com/opensearch-project/opensearch-build/pull/1852](https://github.com/opensearch-project/opensearch-build/pull/1852)

We are still actively working on automating validation and planning to complete it this week. There were additional scope added for OpenSearch Dashboards validation that is delaying the completion of this work  
[https://github.com/opensearch-project/opensearch-build/issues/1555](https://github.com/opensearch-project/opensearch-build/issues/1555)

**Next up**  
• Build, assemble and publish both X64 and ARM 64 RPM artifacts to artifacts storage bucket.  
• Create a new Yum repo to support RPM installation  
• Add Yum repo creation process to OpenSearch distribution workflow  
• Sign the metadata file for Yum repo and RPM package

---

<div class="post-metadata">

**Author:** ![CEHENKLE](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/cehenkle/32/1348_2.png) [@CEHENKLE](https://forum.opensearch.org/u/CEHENKLE)\
**Post date:** [April 8, 2022, 9:45pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/22 "2022-04-08T21:45:00Z")

</div>

Good news. We have finally merged a critical PR to support building different distribution types

**PR’s merged:**

[https://github.com/opensearch-project/opensearch-build/pull/1807](https://github.com/opensearch-project/opensearch-build/pull/1807)

We have also opened a PR to automate RPM validation and its currently under review

[https://github.com/opensearch-project/opensearch-build/pull/1912](https://github.com/opensearch-project/opensearch-build/pull/1912)

**Blockers**

We found a new issue blocking the RPM build generation and working on resolve it now.

[https://github.com/opensearch-project/opensearch-build/issues/1545#issuecomment-1092408321](https://github.com/opensearch-project/opensearch-build/issues/1545#issuecomment-1092408321)

**Next up**

• Merge the automated validation PR and resolve blockers

• Build, assemble and publish both X64 and ARM 64 RPM artifacts to artifacts storage bucket.

• Create a new Yum repo to support RPM installation

• Add Yum repo creation process to OpenSearch distribution workflow

• Sign the metadata file for Yum repo and RPM package

---

<div class="post-metadata">

**Author:** ![CEHENKLE](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/cehenkle/32/1348_2.png) [@CEHENKLE](https://forum.opensearch.org/u/CEHENKLE)\
**Post date:** [April 12, 2022, 1:24am UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/23 "2022-04-12T01:24:31Z")

</div>

Hey;

We’ve hit an issue with the RPM build, and we need to make a decision on whether we want to do some build-fu to get out 1.3.1 in mid-April, or if we want to skip 1.3.1 and go straight to 1.3.2 at the beginning of May.

[https://github.com/opensearch-project/opensearch-build/issues/1545](https://github.com/opensearch-project/opensearch-build/issues/1545)

Details are in the issue, and I’d love to hear your thoughts.

Thanks,  
/C

---

<div class="post-metadata">

**Author:** ![justme](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@justme](https://forum.opensearch.org/u/justme)\
**Post date:** [April 12, 2022, 10:41pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/24 "2022-04-12T22:41:43Z")

</div>

I posted a comment in GH. Earlier comments indicated considerable uncertainty as to when the feature may be ready. GH seems to indicate there may be some clearer data now. Have you found the shift in additional resources assigned to the feature have helped bring the feature to reality? Can you give any updates on plans for the release of this feature?

---

<div class="post-metadata">

**Author:** ![CEHENKLE](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/cehenkle/32/1348_2.png) [@CEHENKLE](https://forum.opensearch.org/u/CEHENKLE)\
**Post date:** [April 14, 2022, 9:24pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/25 "2022-04-14T21:24:14Z")

</div>

Thanks for your comments on the issue. Looking at the amount of hackery we’d have to do/churn on getting the release, we’ll aim to get 2.0-rc1 out first, then release 1.3.2 and all future release on RPM.

Thanks,  
/C

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [April 20, 2022, 6:12pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/26 "2022-04-20T18:12:35Z")

</div>

We are very close to adding the RPM support for OpenSearch 2.0-rc1 version.

Find below the current status

**We are reviewing the PR to add the distribution validation for RPM**  
[https://github.com/opensearch-project/opensearch-build/pull/1912](https://github.com/opensearch-project/opensearch-build/pull/1912)

**We created a new PR to perform integration tests for RPM artifacts and its currently under review**  
[https://github.com/opensearch-project/opensearch-build/pull/2000](https://github.com/opensearch-project/opensearch-build/pull/2000)

We will be starting to generate the RPM release candidate artifacts once the above 2 PR’s are merged.

We will keep this thread updated with the progress.

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [April 27, 2022, 9:30pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/27 "2022-04-27T21:30:10Z")

</div>

Hello all, RPM artifacts are ready to be released with 2.0 RC1 version. We have closed all the necessary PR’s and currently working on closing the (below) last minute issue discovered during our final testing.  
[https://github.com/opensearch-project/opensearch-build/issues/2043](https://github.com/opensearch-project/opensearch-build/issues/2043)

We have finalized the solution for the above issue and we will close it soon. I will keep this thread updated with the progress.

---

<div class="post-metadata">

**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\
**Post date:** [April 27, 2022, 11:05pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/28 "2022-04-27T23:05:47Z")

</div>

thank you @bbarani for keeping the community up to date on this!

---

<div class="post-metadata">

**Author:** ![dinesh](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dinesh/32/3283_2.png) [@dinesh](https://forum.opensearch.org/u/dinesh)\
**Post date:** [April 28, 2022, 8:41pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/29 "2022-04-28T20:41:53Z")

</div>

Thanks @bbarani for the update . Any ETA for the RPM release date ?

if tried with local build on 2.0 RC1 version in MAC and got stuck with some errors and had to create [Opensearch RPM build failing on Mac](https://forum.opensearch.org/t/opensearch-rpm-build-failing-on-mac/9431)  
for help.

Have you seen this error and if yes how did you fix it .

Thanks in advance !

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [April 28, 2022, 9:07pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/30 "2022-04-28T21:07:51Z")

</div>

Hi @dinesh It looks like the errors are due to the fact that you are compiling the distribution on macOS operating system and “LDCONFIG” command doesn’t exist on macOS. This issue should be resolved when compiling on linux. Having said that, our current plan is to [release](https://github.com/opensearch-project/opensearch-build/issues/1624#issuecomment-1111587104) RPM artifacts for 2.0-rc1 build on May 03 2022.

@zhujiaxi has also provided a workaround solution if you need the RPM sooner [here](https://forum.opensearch.org/t/opensearch-rpm-build-failing-on-mac/9431)

---

<div class="post-metadata">

**Author:** ![dinesh](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dinesh/32/3283_2.png) [@dinesh](https://forum.opensearch.org/u/dinesh)\
**Post date:** [April 29, 2022, 7:00am UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/31 "2022-04-29T07:00:23Z")

</div>

Thats a great news @bbarani . Waiting for the official RPM release.  
Manual build is a troublesome due to lots of interdependent platform utilities etc.

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [May 3, 2022, 8:20pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/32 "2022-05-03T20:20:30Z")

</div>

Great news! We have released official version of 2.0-rc1 release today that includes RPM artifacts as well. You can download the RPM artifacts from [Opensearch 2.2.1 · OpenSearch](https://opensearch.org/downloads.html)

We are targeting to publish the RPM artifacts for 1.x series from [1.3.2 release](https://github.com/opensearch-project/opensearch-build/issues/1882) scheduled for May 05 2022. We will keep you updated on the progress.

@dinesh you can download the official RPM artifacts now.

---

<div class="post-metadata">

**Author:** ![dinesh](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dinesh/32/3283_2.png) [@dinesh](https://forum.opensearch.org/u/dinesh)\
**Post date:** [May 4, 2022, 2:40am UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/33 "2022-05-04T02:40:26Z")

</div>

Awesome @bbarani  
Thank you .

I will get back if I face any difficulty installing the same.

---

<div class="post-metadata">

**Author:** ![dinesh](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dinesh/32/3283_2.png) [@dinesh](https://forum.opensearch.org/u/dinesh)\
**Post date:** [May 4, 2022, 1:00pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/34 "2022-05-04T13:00:52Z")

</div>

@bbarani i tried installing in standalone mode and it is working as expected:  
curl -XGET [https://localhost:9200](https://localhost:9200) -u ‘admin:admin’ --insecure  
{  
“name” : “opensearch\_poc”,  
“cluster\_name” : “opensearch”,  
“cluster\_uuid” : “RliApZQ7SQejQMLvd8SE-g”,  
“version” : {  
“distribution” : “opensearch”,  
“number” : “2.0.0-rc1”,  
“build\_type” : “rpm”,  
“build\_hash” : “96802e5699e1eed71ffd5ad5b626adc0d0590f1a”,  
“build\_date” : “2022-04-29T19:55:32.972938565Z”,  
“build\_snapshot” : false,  
“lucene\_version” : “9.1.0”,  
“minimum\_wire\_compatibility\_version” : “7.10.0”,  
“minimum\_index\_compatibility\_version” : “7.0.0”  
},  
“tagline” : “The OpenSearch Project: [https://opensearch.org/](https://opensearch.org/)”  
}

i have few queries though:

1. As version [2.0.0-rc1] is a pre-release version of OpenSearch and is not suitable for production, shall i do further testing on this version or opt for the stable prod version 1.3.2 ?
2. Any tentative timeline for prod version release for 2.0.0 ?
3. Does it make sense to change the .opendistro\_security index name to opensearch\_security , is it something you already have in pipeline?

Thanks again for your support!

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [May 4, 2022, 4:11pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/35 "2022-05-04T16:11:55Z")

</div>

We are planning to release the GA version for 2.0 on May 24th 2022. You can view the version roadmap [here](https://github.com/orgs/opensearch-project/projects/1). You can still test the RC1 version and provide your feedback but its not intended for production.

@davelago Do you have any updates on changing .opendistro\_security index name to opensearch\_security?

---

<div class="post-metadata">

**Author:** ![cliu123](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@cliu123](https://forum.opensearch.org/u/cliu123)\
**Post date:** [May 4, 2022, 6:37pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/36 "2022-05-04T18:37:45Z")

</div>

The decision is not to rename indices: [Renaming, and Backwards Compatibility for Indices · Issue #17 · opensearch-project/opensearch-plugins · GitHub](https://github.com/opensearch-project/opensearch-plugins/issues/17#issuecomment-847204447)

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [May 5, 2022, 6:59pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/37 "2022-05-05T18:59:58Z")

</div>

We have released OpenSearch 1.3.2 version today with RPM artifacts. You can download it using [Opensearch 1.3.2 · OpenSearch](https://opensearch.org/versions/opensearch-1-3-2.html). Let us know if you have any other questions.

@justme @spapadop @oscark Please feel free to test the RPM distribution when you get some time and provide your feedback.

---

<div class="post-metadata">

**Author:** ![justme](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@justme](https://forum.opensearch.org/u/justme)\
**Post date:** [May 6, 2022, 6:32pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/38 "2022-05-06T18:32:29Z")

</div>

I was able to download, but not install since the packages are not signed. This appears to be expected near as I can tell from the RPM status in issue #27. I also know this is an old question, but one I didn’t see ever get answered: Do we know which yum/dnf repo will be distributing the RPMs?

> warning: Downloads/opensearch-1.3.2-linux-x64.rpm: Header V4 RSA/SHA512 Signature, key ID 9310d3fc: NOKEY  
> Verifying… ################################# [100%]  
> Preparing… ################################# [100%]  
> package opensearch-1.3.2-1.x86\_64 does not verify: no digest

---

<div class="post-metadata">

**Author:** ![justme](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@justme](https://forum.opensearch.org/u/justme)\
**Post date:** [May 6, 2022, 6:35pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/39 "2022-05-06T18:35:58Z")

</div>

Actually, I just noticed that #27 is closed despite only 12 of 22 tasks are complete. Why was this closed if it isn’t complete?

---

<div class="post-metadata">

**Author:** ![bbarani](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@bbarani](https://forum.opensearch.org/u/bbarani)\
**Post date:** [May 6, 2022, 6:53pm UTC](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994/40 "2022-05-06T18:53:04Z")

</div>

@justme, we closed the issue as the changes have been completed (and merged) but I realized that some of the individual tasks were just not checked. The open tasks are more related to automation and should not affect the artifacts itself. We are working on automation as a part of enhancement exercise and will be tracked separately. As far as I know, we did [sign](https://github.com/opensearch-project/opensearch-build/issues/1547#issuecomment-1104553208) the yum repo as well as the rpm artifact but I will double check with my development team and confirm soon. You can view the RPM documentation [here](https://opensearch.org/docs/latest/opensearch/install/rpm/)

[Previous page](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994.md?page=1)

[Next page](https://forum.opensearch.org/t/rpm-distributions-delayed-again/6994.md?page=3)
