[Bug 1200953] New: device mapper support gone again in kernel-obs-build
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1200953 Bug ID: 1200953 Summary: device mapper support gone again in kernel-obs-build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: marcus.schaefer@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I maintain a matrix of integration tests to build images in OBS. One part of the tests also builds images using device mapper features like dm-crypt or dm-raid For building such images the OBS worker environment (kernel + initrd) requires support for device mapper modules. For building in OBS the kernel-obs-build package is used. All tests were successful until an update/change of the kernel-obs-build package happened: kernel-obs-build-5.18.2-1.1 For details on the error please visit: * Encrypted image test using dm-crypt osc rbl Virtualization:Appliances:Images:Testing_x86:tumbleweed test-image-luks images x86_64 --- [ 399s] [ DEBUG ]: 13:57:17 | EXEC: [cryptsetup --key-file /var/tmp/kiwi _pt2cp3qu luksOpen /dev/mapper/loop0p3 luksRoot] [ 402s] [ 379.030150][ T4832] device-mapper: table: 254:3: crypt: Error a llocating crypto tfm (-ENOENT) --- * Software raid image test using dm-raid osc rbl Virtualization:Appliances:Images:Testing_x86:tumbleweed test-im age-raid images x86_64 --- [ 137s] modprobe: FATAL: Module md_mod not found in directory /lib/modules /5.18.2-1-default --- The image builds started to fail ~2weeks ago Would be great if this could be fixed. Thanks much -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1200953
https://bugzilla.suse.com/show_bug.cgi?id=1200953#c1
--- Comment #1 from Andreas Schwab
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1200953
https://bugzilla.suse.com/show_bug.cgi?id=1200953#c2
--- Comment #2 from Marcus Sch�fer
kernel-default and kernel-obs-build don't match
A good catch, I think this was the reason why it failed last time too. There was a pending request for kernel-obs-build which was hanging for some reason and that was causing the mismatch. I think think I just need to wait ? Thanks -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1200953
https://bugzilla.suse.com/show_bug.cgi?id=1200953#c3
Jiri Slaby
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1200953
https://bugzilla.suse.com/show_bug.cgi?id=1200953#c4
--- Comment #4 from Marcus Sch�fer
participants (1)
-
bugzilla_noreply@suse.com