Kickstart installer not finding 1.45.6 packaging for el9

Help
,
1

Suggested template:

Problem/Question

Hello, I’ve been installing netdata 1.45.6 with the kickstart installer on RHEL9 for a while now, but recently (reported to me last week) it started to fail, saying that it can’t find this version in the repo. It is able to install 1.46.0 and above, but that version breaks some metric names (otel standardization) which I have not had time to address yet. I would like to continue to install 1.45.6.

This is the install command I’ve used successfully until recently:

sh kickstart.sh --non-interactive --disable-telemetry --release-channel stable --no-updates --dont-start-it --disable-cloud --native-only --install-version 1.45.6*

Relevant docs you followed/actions you took to solve the issue

I saw a notice in the documentation about repositories changing in late 2024, but I don’t know what it means and if it has any bearing on my situation. It was the only relevant notice I could find.

“In July 2022, we switched hosting of our native packages from Package Cloud to self-hosted repositories. Until late 2024 we continued to provide packages via Package Cloud, but we have since then switched to only providing packages via our repositories.”

Environment/Browser/Agent’s version etc

I’m focusing on installs for RHEL9 at the moment, but will also need 1.45.6 for Ubuntu 22 as well.

What I expected to happen

I would like to be able to continue to install version 1.45.6. Thanks!

2

This is expected but I believe not currently documented. Storage unfortunately isn’t free, so we can’t keep all old versions of Netdata in our native package repositories forever. As of right now, the current retention policy we have for native packages is:

  • For nightly builds, packages are only kept for 30 days.
  • For stable releases, packages are only kept for the five most recent major/minor releases (as of writing this comment, this covers 1.46, 1.47, 2.0, 2.1, and 2.2) and all patch releases for those versions.

We need to reevaluate this policy in the near future anyway since our release cadence has changed significantly since it was put in place, so I will make a point to bring up user interest in keeping older versions available longer when we review the policy.

3

Thanks for the quick response, and good to know about the five most recent major/minor releases.

I’ll work on updating to a newer version.

Thanks again