Resolve systemd-dbus Package Installation Conflicts

Resolve systemd-dbus Package Installation Conflicts

During ODP package installation, Ambari might fail to install the python*-systemd-dbus package because of an incorrect package naming convention in the Mpack metadata files.

This issue occurs when the package name includes the ${stack_version} suffix, which prevents the package manager from locating the required package.

Error

The following error might appear during package installation:

Package Manager failed to install packages:
No package found for python*-systemd-dbus_${stack_version}
(expected name: python*-systemd-dbus_3_3_6_6_1010)

Resolution

To resolve the package installation issue, update the package name in the affected Mpack metadata files.

1. Navigate to the Mpack directory on the Ambari Server host:

cd /var/lib/ambari-server/resources/mpacks/

2. Identify the files that reference systemd-dbus:

grep -irn "systemd-dbus" .

3. The command displays the matching files and line numbers. The affected Mpacks might include Impala, JupyterHub, Kudu, and Trino.
4. Back up the Mpack directory before modifying the metadata files:

cp -a /var/lib/ambari-server/resources/mpacks /var/lib/ambari-server/resources/mpacks.bak

5. Run the following command to replace python*-systemd-dbus_${stack_version} with python*-systemd-dbus in the affected files:

grep -rl 'python\*-systemd-dbus_${stack_version}' . | while read -r f; do
  sed -i 's/python\*-systemd-dbus_\${stack_version}/python*-systemd-dbus/g' "$f"
done

6. Verify that the package names have been updated:

grep -rn 'systemd-dbus' .

7. The updated entries should use the following package name without the stack version suffix:

<name>python*-systemd-dbus</name>

8. Restart the Ambari Server to apply the changes:

ambari-server restart

9. Retry the failed package installation from the Ambari UI.
   Verify that the required packages are installed successfully.