[Bug 1195775] New: apparmor fails to build with 5.16.7
https://bugzilla.suse.com/show_bug.cgi?id=1195775 Bug ID: 1195775 Summary: apparmor fails to build with 5.16.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jslaby@suse.com Reporter: jslaby@suse.com QA Contact: qa-bugs@suse.de CC: dimstar@opensuse.org, suse-beta@cboltz.de Found By: --- Blocker: --- This is a failure in openSUSE:Factory:Staging:K:
[ 133s] + parser/apparmor_parser --config-file /home/abuild/rpmbuild/BUILD/apparmor-3.0.3/parser/parser.conf --write-cache -QT -L /home/abuild/rpmbuild/BUILD/apparmor-3.0.3/profiles/cache -I profiles/apparmor.d/ profiles/apparmor.d/ [ 133s] Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.) ... [ 138s] + cp -a 'profiles/cache/*' /home/abuild/rpmbuild/BUILDROOT/apparmor-3.0.3-10.3.x86_64/usr/share/apparmor/cache [ 138s] cp: cannot stat 'profiles/cache/*': No such file or directory [ 138s] error: Bad exit status from /var/tmp/rpm-tmp.Q3LG8a (%install)
Likely missing systemd in kernel-obs-build (commit ef4c569b9986) causes /sys/kernel/security not to be mounted and: 8873 newfstatat(-1, "/sys/kernel/security/apparmor/features", 0x7ffec91f0d00, 0) = -1 ENOENT (No such file or directory) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c1
Jiri Slaby
Likely missing systemd in kernel-obs-build (commit ef4c569b9986) causes /sys/kernel/security not to be mounted and:
Confirmed. The commit causes the issue, so reverted in stable and resubmitted. Michal, it should be reverted in packaging likely too, IMO. Dirk, not sure if you want to work around it somehow, handing over to you, if you want to retry or not. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c2
--- Comment #2 from Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c3
--- Comment #3 from Michal Suchanek
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c4
--- Comment #4 from Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c5
--- Comment #5 from Jiri Slaby
133:systemd-mini-249.9-4.1 warning: group systemd-journal does not exist - using root ################################# [ 77%] Failed to open 'systemd.conf', ignoring: No such file or directory Running in chroot, ignoring command 'daemon-reexec' /usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping All rules containing unresolvable specifiers will be skipped. /usr/lib/tmpfiles.d/suse.conf:10: Failed to resolve group 'lock'. /usr/lib/tmpfiles.d/suse.conf:13: Failed to resolve group 'utmp'. /usr/lib/tmpfiles.d/suse.conf:14: Failed to resolve group 'utmp'. /usr/lib/tmpfiles.d/suse.conf:15: Failed to resolve group 'utmp'. /usr/lib/tmpfiles.d/systemd.conf:22: Failed to resolve group 'systemd-journal'. /usr/lib/tmpfiles.d/systemd.conf:25: Failed to resolve group 'systemd-journal'. /var/tmp/rpm-tmp.ye6FKZ: line 70: /usr/lib/systemd/systemd-sysv-convert: No such file or directory /var/tmp/rpm-tmp.ye6FKZ: line 82: /usr/lib/systemd/systemd-sysv-convert: No such file or directory /var/tmp/rpm-tmp.ye6FKZ: line 94: /usr/lib/systemd/systemd-sysv-convert: No such file or directory /var/tmp/rpm-tmp.ye6FKZ: line 106: /usr/lib/systemd/systemd-sysv-convert: No such file or directory /var/tmp/rpm-tmp.ye6FKZ: line 118: /usr/lib/systemd/systemd-sysv-convert: No such file or directory
And finally:
Executing interactive shell... -bash: cannot set terminal process group (-1): Inappropriate ioctl for device -bash: no job control in this shell
And it then gives one a shell, but without systemd and job control. (systemd likely switches consoles, so that job control works in bash.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c6
--- Comment #6 from Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c7
--- Comment #7 from Jiri Slaby
I intend to fix that in the build script. please revert the reversion. its gonna be deployed today.
https://github.com/openSUSE/obs-build/commit/ aad3043d486332a51ea3d2de75031757c06883a9 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c8
--- Comment #8 from Jiri Slaby
how do you get this ? I use osc shell (on vm-type=kvm) for many months with this kernel change in my home.
I think nothing special: osc shell --root=/dev/shm/jslaby/xxvm --no-service --no-verify --disable-debug --download-api-only -x vim -x vim-data -x strace -x telnet-server --vm-memory=20000 --vm-type=kvm --vm-telnet=30000 -p ~/tmp/rpms/ where ~/tmp/rpms/ contains kernel-obs-build built with the change. (Otherwise I don't see the issue, of course.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c9
Dirk Mueller
(In reply to Dirk Mueller from comment #6)
how do you get this ? I use osc shell (on vm-type=kvm) for many months with this kernel change in my home.
I think nothing special: osc shell --root=/dev/shm/jslaby/xxvm --no-service --no-verify --disable-debug --download-api-only -x vim -x vim-data -x strace -x telnet-server --vm-memory=20000 --vm-type=kvm --vm-telnet=30000 -p ~/tmp/rpms/
ah, you're using telnet, thats why. I'll work on this when I find a bit of time over hte next few days (not today). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c10
--- Comment #10 from Jiri Slaby
(In reply to Jiri Slaby from comment #8)
(In reply to Dirk Mueller from comment #6)
how do you get this ? I use osc shell (on vm-type=kvm) for many months with this kernel change in my home.
I think nothing special: osc shell --root=/dev/shm/jslaby/xxvm --no-service --no-verify --disable-debug --download-api-only -x vim -x vim-data -x strace -x telnet-server --vm-memory=20000 --vm-type=kvm --vm-telnet=30000 -p ~/tmp/rpms/
ah, you're using telnet, thats why. I'll work on this when I find a bit of time over hte next few days (not today).
As you've noticed I tried again :). Apart from this, some packages need iproute2. Going to revert for now -- will retry some time later. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c11
--- Comment #11 from Jiri Slaby
Going to revert for now -- will retry some time later.
Wait, is:
commit d9a821b1f81a10afa444c382bdb364f65ca861c7
Author: Dirk M�ller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c12
--- Comment #12 from Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c13
Jiri Slaby
yes, it is. the iproute2 dependency is new, it was stripped from factory config because due to your revert the issue was hidden.
I think you still need iproute2 in the build env for -vm-telnet to work, so I think the prjconf change should be reverted, which would fix the kernel build failure. I had a discussion about that in irc but it was inconclusive.
So now I don't know. Should I revert the kernel change or will someone fix the iproute2 failure in factory's prjconf? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c14
--- Comment #14 from Jiri Slaby
So now I don't know. Should I revert the kernel change or will someone fix the iproute2 failure in factory's prjconf?
Ok, there is another failure in kernel-obs-qa. The kernel-obs-build kernel does not boot: [ 97s] [[0;1;31m TIME [0m] Timed out waiting for device [0;1;39m/dev/disk/by-id/virtio-0[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39m/sysroot[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mInitrd Root File System[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mRelo���figuration from the Real Root[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mInitrd Root Device[0m. I reverted the change again. And I'm not sure the change is worth all the trouble. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c15
Fabian Vogt
(In reply to Jiri Slaby from comment #13)
So now I don't know. Should I revert the kernel change or will someone fix the iproute2 failure in factory's prjconf?
Ok, there is another failure in kernel-obs-qa. The kernel-obs-build kernel does not boot: [ 97s] [[0;1;31m TIME [0m] Timed out waiting for device [0;1;39m/dev/disk/by-id/virtio-0[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39m/sysroot[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mInitrd Root File System[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mRelo���figuration from the Real Root[0m. [ 97s] [[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mInitrd Root Device[0m.
I reverted the change again. And I'm not sure the change is worth all the trouble.
Apparently the initrd includes systemd-initrd, but not dracut-systemd, so it's missing important stuff like the pre-udev hook. Without that, 80obs won't run for instance and kernel modules aren't loaded. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c16
Dirk Mueller
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c40
--- Comment #40 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c42
--- Comment #42 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c43
--- Comment #43 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c44
--- Comment #44 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c46
--- Comment #46 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c48
--- Comment #48 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c50
--- Comment #50 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c58
--- Comment #58 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c59
--- Comment #59 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c60
--- Comment #60 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c61
--- Comment #61 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c62
--- Comment #62 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c63
--- Comment #63 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c65
--- Comment #65 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c66
--- Comment #66 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c67
--- Comment #67 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1195775
https://bugzilla.suse.com/show_bug.cgi?id=1195775#c68
--- Comment #68 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@suse.com