Skip to content

Conversation

@joseivanlopez
Copy link
Contributor

@joseivanlopez joseivanlopez commented Jul 17, 2025

Problem

Some services interfers with libstorage-ng activation.

https://bugzilla.suse.com/show_bug.cgi?id=1246133

Solution

Disable services. Mask the services. Disabling them was not enough.

@ancorgs
Copy link
Contributor

ancorgs commented Jul 17, 2025

According to my experiments, it is not necessary to disable systemd-udev.service in order to fix bsc#1246133.

So I will add a commit removing that service from the list. We want to release a new version of Agama (and its corresponding live image) next week, so I prefer to keep changes to the minimum necessary.

@ancorgs
Copy link
Contributor

ancorgs commented Jul 17, 2025

So I will add a commit removing that service from the list.

Turns out disabling only lvm2-monitor.service and lvm-activate-system.service was not enough. So I will run some more experiments.

@ancorgs ancorgs force-pushed the live-disable-storage branch 4 times, most recently from 8124216 to ae8229a Compare July 17, 2025 21:15
@ancorgs
Copy link
Contributor

ancorgs commented Jul 17, 2025

Ok. Let me make a summary.

First of all, the third line would be systemd-udevd.service instead of systemd-udev.service. But it doesn't work anyways.

I used this pull request as a base to do several unsuccessful experiments:

  1. Disabling lvm2-monitor.service and lvm-activate-system.service. It didn't work because systemd-udevd.service still fiddles with lvm.
  2. Disabling lvm2-monitor.service, lvm-activate-system.service and systemd-udevd.service. It didn't work because systemd-udevd.service was triggered by systemd-udevd-kernel.socket and systemd-udevd-control.socket. And then it fiddled with lvm.
  3. Disabling lvm2-monitor.service, lvm-activate-system.service, systemd-udevd.service, systemd-udevd-kernel.socket and systemd-udevd-control.socket. It didn't work. The behavior was identical to the previous case.
  4. Masking (not only disabling) lvm2-monitor.service, lvm-activate-system.service and systemd-udevd.service. It didn't work because the system was not even able to configure the network.

I'm running a final experiment before giving up and leaving this for the next tester.

@ancorgs
Copy link
Contributor

ancorgs commented Jul 17, 2025

Looks like I finally found the option that works: masking (not disabling) lvm2-monitor.service and lvm-activate-system.service.

I'm pretty sure we don't need them because libstorage-ng will take care of activating LVM. I'm also pretty sure that disabling them is not enough.

So I modified this pull request according to those findings.

@ancorgs ancorgs marked this pull request as ready for review July 17, 2025 21:53
Copy link
Contributor

@ancorgs ancorgs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I manually checked this and works as expected. I was able to complete the installation in a multipath system with a previous LVM and everything was correctly detected and later installed.

@ancorgs ancorgs merged commit c3ed29e into agama-project:master Jul 17, 2025
1 check passed
@imobachgs imobachgs mentioned this pull request Jul 21, 2025
imobachgs added a commit that referenced this pull request Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants