Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime-cleanup: don't strip device-mapper-event #1328

Closed
wants to merge 1 commit into from
Closed

runtime-cleanup: don't strip device-mapper-event #1328

wants to merge 1 commit into from

Commits on Jun 17, 2023

  1. runtime-cleanup: don't strip device-mapper-event 

    The openQA install_blivet_lvmthin test - which, as the name
implies, does an LVM thinp install - is consistently failing
(only on ppc64le, for some reason). The logs show that lvm2 is
trying to run dmeventd as part of some kind of check of the
pool, but it's failing because dmeventd isn't there:

Failed to call the 'LvCreate' method on the '/com/redhat/lvmdbus1/ThinPool/0' object: GDBus.Error:org.freedesktop.DBus.Python.dbus.exceptions.DBusException: ('com.redhat.lvmdbus1.Lv', 'Exit code 5, stderr = /usr/sbin/dmeventd: stat failed: No such file or directory, /usr/sbin/dmeventd: stat failed: No such file or directory, Check of pool fedora/00 failed (status:64). Manual repair required!, Failed to activate thin pool fedora/00.')

So, apparently we do need this now. Whether to use dmeventd or
not seems to be a build time check/config option for lvm2, but
I don't think we can turn that off just to save a bit of space
in the installer image - the package is only about 50K.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
    @AdamWill
    AdamWill committed Jun 17, 2023
    Configuration menu
    Copy the full SHA
    0bd7f38 View commit details
    Browse the repository at this point in the history