Bug 1871986

Summary: lvm2-lvmetad.socket: Failed to load configuration: No such file or directory
Product: [Fedora] Fedora Reporter: Artem <ego.cordatus>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: agk, anprice, awilliam, bmarzins, bmr, cfeist, heinzm, jonathan, kzak, lvm-team, mcsontos, msnitzer, prajnoha, prockai, robatino, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-25 17:08:41 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:
Bug Depends On:    
Bug Blocks: 1766775    
Attachments:
Description Flags
journal none

Description Artem 2020-08-24 19:02:54 UTC
Created attachment 1712423 [details]
journal

Description of problem:
After upgrade to f33 from f32 can't boot my system anymore because of this errors during boot:

  lvm2-lvmetad.socket: Failed to load configuration: No such file or directory

  Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/lvm2_2dlvmetad_2esocket interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=432351 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a


Version-Release number of selected component (if applicable):
lvm2-2.03.10-1.fc33


How reproducible:
Do system upgrade from f32 -> f33.


Actual results:
System won't boot anymore.


Expected results:
Successful boot and functional system.


Additional info:
Note #1: Doesn't have any LVM partition on my system.
Note #2: Tried to disable all then enable all lvm2 and raid systemd services — no luck.
Note #3: Tried to remove completely 'lvm2' package but issue is still here.
Note #4: Attached full journal log with 'debug'.

Comment 1 Artem 2020-08-24 23:33:23 UTC
Seems like i found what causing this — there is leftover systemd units symlinks on non-exists units even after removing 'lvm2' package:

  etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket -> /usr/lib/systemd/system/lvm2-lvmetad.socket

After manually removing 'etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket' symlink system boots fine. I found in lvm2 changelog that there already was some mentions such as:

  "Use RemoveOnStop for lvm2-lvmetad.socket systemd unit."

but something goes wrong probably.

Comment 2 Adam Williamson 2020-08-25 17:08:41 UTC
I think this and your other bug are almost certainly the same thing, so let's dupe them.

*** This bug has been marked as a duplicate of bug 1872068 ***