Bug 1697548

Summary: After upgrade systemd to 242~rc3-1.fc31 system became unworkable
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jpokorny, lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
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: 2019-04-10 21:50:55 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:
Attachments:
Description Flags
system log (with systemd 242~rc3-1) none

Description Mikhail 2019-04-08 16:12:57 UTC
Created attachment 1553673 [details]
system log (with systemd 242~rc3-1)

Description of problem:
After upgrade systemd to 242~rc3-1.fc31 system became unworkable

Last working systemd version is systemd-241-4.gitcbf14c9

Comment 1 Mikhail 2019-04-08 16:16:19 UTC
For everybody who experienced this issue for restoring system is insufficient only downgrade systemd to 241-4.gitcbf14c9 you also should disable SELinux.

Comment 2 Jan Pokorný [poki] 2019-04-08 22:18:30 UTC
Duplicate of [bug 1697370]?

Comment 3 Zbigniew Jędrzejewski-Szmek 2019-04-10 21:50:55 UTC
1697667 shows the same AVCs. Seems to be the same issue.

Apr 08 20:10:11 localhost.localdomain systemd-coredump[941]: Process 925 (ebtables) of user 0 dumped core.
                                                             
                                                             Stack trace of thread 925:
                                                             #0  0x00007fec0f04a40f dirname (libc.so.6)
                                                             #1  0x00007fec0f1218c0 ebt_get_kernel_table (libebtc.so.0)
                                                             #2  0x00007fec0f11e5ff do_command (libebtc.so.0)
                                                             #3  0x00005610302470e1 n/a (ebtables-legacy)
                                                             #4  0x00007fec0ef75f73 __libc_start_main (libc.so.6)
                                                             #5  0x000056103024711e n/a (ebtables-legacy)

You probably should report that separate if you haven't yet.

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

Comment 4 Jan Pokorný [poki] 2019-04-10 22:50:03 UTC
re [comment 3]:

> Stack trace of thread 925:
> #0  0x00007fec0f04a40f dirname (libc.so.6)
> #1  0x00007fec0f1218c0 ebt_get_kernel_table (libebtc.so.0)
> #2  0x00007fec0f11e5ff do_command (libebtc.so.0)
> #3  0x00005610302470e1 n/a (ebtables-legacy)
> #4  0x00007fec0ef75f73 __libc_start_main (libc.so.6)
> #5  0x000056103024711e n/a (ebtables-legacy)

Possibly fixed along with [bug 1697569].