Bug 2044446 - Multipathd service failing to start due libgcc update
Summary: Multipathd service failing to start due libgcc update
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2022-01-24 16:14 UTC by Renata Ravanelli
Modified: 2022-02-01 13:46 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-01 13:46:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Renata Ravanelli 2022-01-24 16:14:06 UTC
Description of problem:

Multipath won't start automatically with libgcc-12.0.0-0.5.fc36


Version-Release number of selected component (if applicable):
libgcc-12.0.0-0.5.fc36

How reproducible:
Install rawhide using libgcc-12.0.0-0.5.fc36

Actual results:
Multipath service will fail to start:

[core@cosa-devsh ~]$ systemctl status multipathd.service | cat
× multipathd.service - Device-Mapper Multipath Device Controller
     Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Wed 2022-01-19 02:55:16 UTC; 1min 14s ago
TriggeredBy: ○ multipathd.socket
  Condition: start condition failed at Wed 2022-01-19 02:55:44 UTC; 46s ago
             └─ ConditionPathExists=/etc/multipath.conf was not met
   Main PID: 553 (code=killed, signal=SEGV)
        CPU: 67ms

Jan 19 02:55:16 localhost systemd[1]: Starting multipathd.service - Device-Mapper Multipath Device Controller...
Jan 19 02:55:16 localhost systemd[1]: Started multipathd.service - Device-Mapper Multipath Device Controller.
Jan 19 02:55:16 localhost systemd[1]: multipathd.service: Main process exited, code=killed, status=11/SEGV
Jan 19 02:55:16 localhost systemd[1]: multipathd.service: Failed with result 'signal'.
Jan 19 02:55:44 localhost systemd[1]: multipathd.service - Device-Mapper Multipath Device Controller was skipped because of a failed condition check (ConditionPathExists=/etc/multipath.conf).



Expected results:
Multipath service up

Additional info:
[core@cosa-devsh ~]$ systemctl list-dependencies multipathd.service
multipathd.service
● ├─system.slice
● ├─systemd-udev-settle.service
● └─systemd-udev-trigger.service


root@cosa-devsh core]#  multipath -l
81.831023 | /etc/multipath.conf does not exist, blacklisting all devices.
81.832247 | You can run "/sbin/mpathconf --enable" to create
81.833176 | /etc/multipath.conf. See man mpathconf(8) for more details

[root@cosa-devsh core]# /sbin/mpathconf
multipath is enabled
find_multipaths is yes
user_friendly_names is enabled
default property blacklist is disabled
enable_foreign is not set (no foreign multipath devices will be shown)
dm_multipath module is loaded
multipathd is not running

[root@cosa-devsh core]# /sbin/mpathconf --enable
[root@cosa-devsh core]# multipath -l


There is a segfault happening in the initramfs, when the service is stopping:

Jan 18 23:43:44.154727 multipathd[442]: exit (signal)
Jan 18 23:43:44.154727 multipathd[442]: --------shut down-------
Jan 18 23:43:44.149000 audit[442]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=442 comm="multipathd" exe="/usr/sbin/multipathd" sig=11 res=1
Jan 18 23:43:44.236235 systemd[1]: Reached target initrd-fs.target - Initrd File Systems.
Jan 18 23:43:44.244684 systemd[1]: Reached target initrd.target - Initrd Default Target.
Jan 18 23:43:44.281778 systemd-coredump[733]: Failed to connect to coredump service: No such file or directory
Jan 18 23:43:44.457878 systemd[1]: multipathd.service: Main process exited, code=killed, status=11/SEGV
Jan 18 23:43:44.463689 systemd[1]: multipathd.service: Failed with result 'signal'.
Jan 18 23:43:44.472406 systemd[1]: Stopped multipathd.service - Device-Mapper Multipath Device Controller.

More info:  https://github.com/coreos/fedora-coreos-tracker/issues/1071

Comment 1 Paul Whalen 2022-01-27 21:34:29 UTC
No longer seeing this failure as of Fedora-Rawhide-20220127.n.0, which includes libgcc-12.0.1-0.3.fc36.aarch64.

Comment 2 Dusty Mabe 2022-01-28 02:02:48 UTC
Same for us in Fedora CoreOS land. See https://github.com/coreos/fedora-coreos-tracker/issues/1071#issuecomment-1023650686

Comment 3 Jakub Jelinek 2022-02-01 13:46:02 UTC
Fixed then.


Note You need to log in before you can comment on or make changes to this bug.