Bug 1631772
| Summary: | multipathd: "errors" during normal boot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> | ||||
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 29 | CC: | agk, bmarzins, cfeist, heinzm, kzak, lvm-team, mcsontos, msnitzer, prajnoha, samuel-rhbugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | device-mapper-multipath-0.7.7-6.gitef6d98b.fc29 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-01-18 02:13:58 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Zbigniew Jędrzejewski-Szmek
2018-09-21 14:22:35 UTC
This only happens when manually running multipathd, correct? Manually starting multipathd without a configuration file is not completely mundade. It's something that should never happen. Systemd refuses to start the service because of ConditionPathExists=/etc/multipath.conf in multipathd.service Which will keep you from ever seeing this message. So, unless I'm missing something, you have to manually run multipathd to see this, which you should not be doing anyway. You should start it via systemd. I would argue that if someone thinks that they have correctly started multipathd but they haven't, that's important information. Is there some situation during boot where something is trying to start multipathd not through systemd? I omitted an important bit of information: this is on silverblue (F29-beta5 amd64 silverblue image under qemu). This might or might not be relevant.
> This only happens when manually running multipathd, correct?
No, I'm not starting anything manually. This error message is from the logs from a default boot after installation.
The .service has ConditionPathExists=/etc/multipath.conf, but .socket does not. I guess the service is started when something connects to the socket.
Created attachment 1520673 [details]
screenshot from qemu boot
Can we please get this fixed? When booting a Workstation-live image (and xfce, and probably others), this is prominently visible during but and *very* ugly. People are putting a lot of effort into polish, and stuff like this completely defeats it.
Please see attached screenshot from
qemu-system-x86_64 -machine accel=kvm -smp 2 -m 2048 -drive if=pflash,format=raw,readonly,file=/usr/share/edk2/ovmf/OVMF_CODE.fd -cdrom Workstation-Live-x86_64-Rawhide-20190114.n.0.iso
device-mapper-multipath-0.7.7-6.gitef6d98b.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e969fe2844 device-mapper-multipath-0.7.7-6.gitef6d98b.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e969fe2844 device-mapper-multipath-0.7.7-6.gitef6d98b.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. Appears to be a problem still, on today's Fedora 30 beta. I saw that msg on screen while booting the fedora live media |