-
Notifications
You must be signed in to change notification settings - Fork 175
13.3.3 rpm not available via Yum #796
Comments
I tried the tarball upgrade and my test node will not stay connected to the cluster even when the proper configs are in place. Are there any plans for a RPM package? |
can we get some eyes on this, I would love to update my cluster... |
I am facing same issue.. 1.13.3 is not available for RPM . |
i have manually updated all log4j jars to version 2.16.0 ... i see cluster started with out issues .. below is the location of jars .. |
I am facing same issue with Kibana.
I am getting "Access Denied" when I try to download tarball with this link: |
Same issue here, I guess this is a problem with cloudfront distribution's TTL.
It is a problem because of security (for sure) but also because documentation is pointing users to install 1.13.3 via yum, and it won't work. |
Even when I downloaded the tar.gz for 1.13.3, the log4j versions were not updated in that. I'm not sure what's going on with the distribution, but we ended up doing things manually. I made a bash script that updated our Elasticsearch and Logstash versions. I put up a github gist if anyone wants to look at it. Use at your own risk. It worked for me, but I make no guarantees for anyone else. https://gist.github.com/jdratlif/46ac9070387d96cc8855a4cd775ad798 |
Thanks everyone for your patience. And thanks, @jdratlif for the script! We're aware of this issue and working on a plan. Hang tight, we'll update you on the plan after the holidays. |
@Jon-AtAWS Hate to be a bother but any timeline for the rpm fixes? |
Hi @ravenbyron , sorry we didn't close this out in this issue. We looked really hard at different ways to produce an Open Distro 1.13.3 RPM release, and the conclusion we came to is that it simply isn't possible. The Open Distro RPM releases were based on upstream RPM releases, and no upstream RPM release was produced that includes a fix. The Log4j dependency is in Elasticsearch itself. The Log4j website describes several remediations cluster admins can perform today, and we've published guidance on the Open Distro website with links to resources to support migrating to OpenSearch, which is patched against the high-severity Log4J CVEs from the past several weeks. |
Did a yum update, fresh box following the rpm instructions, and repo list and not seeing 13.3.3 available
edit: Also building rpm from source is building it as 1.13.2
The text was updated successfully, but these errors were encountered: