Skip to main content

Documentation Portal

Preventing Helm Version Conflicts During TrendMiner Upgrades

This article applies to self-hosted deployments only.

Overview

TrendMiner requires Helm v3, which is included in the TrendMiner upgrade package. While TrendMiner only needs the standard RHEL or AlmaLinux repositories, conflicts can arise if additional repositories are enabled on your system that also contain Helm packages. Running dnf update with these additional repositories enabled may upgrade Helm to v4, causing the TrendMiner upgrade to fail.

When an upgrade fails on this issue you can recognize it by a failure of the configure-tm-agent step. When inspecting the reason of the failure (by clicking on the failure message) you'll see the following error:

TASK [Deploy helm chart for <service name>] ********************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ValueError: too many values to unpack (expected 3) fatal: ...

A well-known example of a repo which contains helm is the epel repo which is required during the initial TrendMiner installation but should be disabled as soon as TrendMiner is installed, as documented in the installation guide.

Checking Your Current Helm Version

Before proceeding with a TrendMiner upgrade, verify your installed Helm version: helm version

If the output shows Helm v4, you'll need to downgrade to v3 before upgrading TrendMiner.

Repository Configuration

Verify Enabled Repositories

Check which repositories are currently enabled on your system: dnf repolist --enabled

Expected Repository Configuration

Your system should only have the following repositories enabled:

For AlmaLinux 9:

  • AlmaLinux 9 - BaseOS

  • AlmaLinux 9 - Extras

  • AlmaLinux 9 - AppStream

For RHEL 9:

  • rhel-9-for-x86_64-appstream-rpms

  • rhel-9-for-x86_64-baseos-rpms

Disable Additional Repositories

If you see any repositories beyond those listed above, disable them using: dnf config-manager --set-disabled <repo_name> or subscription-manager repos --disable <repo_name>

Replace <repo_name> with the name of each additional repository that appears in your enabled list.

Downgrading from Helm v4 to v3

If you've already upgraded to Helm v4, follow these steps to downgrade:

  1. Ensure only the standard repositories are enabled (see above)

  2. Remove the current Helm installation: dnf remove helm

  3. Temporarily enable the tm-appliance repo to install Helm v3: dnf config-manager --set-enabled tm-appliance

  4. Install Helm v3 from the tm-appliance repo: dnf install helm

  5. Verify you helm version is now v3: helm version

  6. Disable again the tm-appliance repo: dnf config-manager --set-disabled tm-appliance

  7. Retry your TrendMiner upgrade.

Best Practice for TrendMiner Upgrades

To prevent (Helm) version conflicts during future upgrades:

  1. Before running dnf update, verify that only the standard RHEL or AlmaLinux repositories are enabled

  2. Disable any third-party repositories that might contain conflicting (Helm) packages.

  3. Refer to the TrendMiner installation documentation for the complete list of approved repositories

FAQs

  • Q: I've always had other repos enabled and my upgrade did not fail before. How come it failed now?

    A: In November 2025 the v4 version of Helm was released which contains breaking changes. Before v4 of helm was released the helm version in TrendMiner and other repos were compatible and it would go unnoticed if other repos are enabled.

  • Q: I'm running TrendMiner on a private cloud instance (e.g. Azure) which requires additional repos to be enabled.

    A: As long as these repos do not contain conflicting package versions having them enabled should not cause issues. To prevent package conflicts it is advised to temporarily disable these repos before running a dnf update. To check if a repo contains the Helm package run: dnf repo-packages <repo name> list available | grep helm

  • Q: I need other repos enabled for other software I'm running on my server.

    A: To avoid package conflicts (among other things) the installation of other software like monitor tools and agents (e.g. virus scanners ) on a TrendMiner Single Node setup is not supported as mentioned in our installation guide. Contact TrendMiner support in case you have conflicting company requirements.

In this section: