ibacm service fails if ub_umad module is not loaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rdma-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* The service for ibacm needs special HW to be present
* The sysV service has no way to express any such dependencies but dh*
tools will start it in postinst. Due to that the service will fail to
start.
* That makes DPDK think the installation failed in general (bad RC on
service start)
* We went back and forth upstream and in Debian (same people) but the
solution seems to be to get rid of the sysV file.
[Test Case]
* 1. Get to a system that has no infiniband HW and due to that module
ub_umad not loaded (any container will do).
* 2. install ibacm
Without fix:
Configuring ibacm (17.1-1) ...
Job for ibacm.service failed because the control process exited with
error code.
See "systemctl status ibacm.service" and "journalctl -xe" for details.
invoke-rc.d: initscript ibacm, action "start" failed.
● ibacm.service - InfiniBand Address Cache Manager Daemon
Active: failed[...]
* With the fix the install will work
For the unlikely case that you have all an IB capable system the
service will load later when the socket is connected (via rdma)
ListenNet
[Regression Potential]
* If somebody used the non recommended sysV init script directly it will
after the upgrade be removed and therefore non-functional.
Other than that nobody should miss anything, as everything else stays
as-is.
[Other Info]
* I'm open for discussion, we might decide to NOT rm_conffile the sysV
script for SRUs if that would be preferred by the SRU Team - let me
know in that case.
---
Hello
In upgrade someone packages didn't intalled, i don't know anymore
(sorry my bad english)
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ibacm 17.1-1
ProcVersionSign
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
libudisks2-
NULL: ConfigurePending
Architecture: amd64
Date: Thu Sep 27 17:40:26 2018
ErrorMessage: instalado ibacm paquete post-installation guión el subproceso devolvió un error con estado de salida 1
InstallationDate: Installed on 2018-05-19 (131 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.3ubuntu0.1
SourcePackage: rdma-core
Title: package ibacm 17.1-1 failed to install/upgrade: instalado ibacm paquete post-installation guión el subproceso devolvió un error con estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in rdma-core (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in rdma-core (Ubuntu Cosmic): | |
status: | New → Triaged |
Interesting, thanks for the report.
It seems it breaks to start the service /lib/systemd/ system/ ibacm.service due to /sys/class/ infiniband_ mad/abi_ version not being available.
That alone is a reasonable error, as the daemon is meant to be the "InfiniBand Address Cache Manager Daemon" and it can't work well without the backend being loaded.
The backend in this case is a kernel module "ib_umad".
As soon as that is loaded the start of the service works.
I'd recommend that (loading the module manually) to you as a workaround for now.
But for the package we'd want to have defaults safe and working, and in case the module isn't loaded I'd expect it to not start at all or load it on demand.