This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Booting in permissive and restarting systemd-logind in both permissive and enforcing (mls) seems to work without errors - the logind process is running and I see no tracebacks in 'journalctl -u systemd-logind' and no AVCs in audit log.

I cannot log in via serial console in enforcing due to

Cannot make/remove an entry for the specified session

but as far as I can tell, this is not the logind issue described above.

Sorry, wrong bug, please ignore the logind stuff in comment 3. Regardless of that, I still cannot log in via serial console on F25.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Trying this on F27, it still doesn't work.

The login process stops on

----
time->Mon Mar 12 12:18:49 2018
type=PROCTITLE msg=audit(1520853529.335:876): proctitle=2F62696E2F6C6F67696E002D70002D2D0020202020
type=SYSCALL msg=audit(1520853529.335:876): arch=c000003e syscall=1 success=no exit=-13 a0=4 a1=55851f593cd0 a2=27 a3=0 items=0 ppid=1 pid=1506 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=ttyS0 ses=7 comm="login" exe="/usr/bin/login" subj=system_u:system_r:local_login_t:s15:c0.c1023 key=(null)
type=AVC msg=audit(1520853529.335:876): avc:  denied  { create } for  pid=1506 comm="login" scontext=system_u:system_r:local_login_t:s15:c0.c1023 tcontext=root:sysadm_r:sysadm_t:s0-s15:c0.c1023 tclass=key permissive=0


and if I allow it via permissive, it goes on to:

----
time->Mon Mar 12 12:15:42 2018
type=PROCTITLE msg=audit(1520853342.035:793): proctitle=2F62696E2F6C6F67696E002D70002D2D0020202020
type=SYSCALL msg=audit(1520853342.035:793): arch=c000003e syscall=1 success=yes exit=39 a0=4 a1=5575520cfcd0 a2=27 a3=0 items=0 ppid=1 pid=1427 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=ttyS0 ses=5 comm="login" exe="/usr/bin/login" subj=system_u:system_r:local_login_t:s15:c0.c1023 key=(null)
type=AVC msg=audit(1520853342.035:793): avc:  denied  { create } for  pid=1427 comm="login" scontext=system_u:system_r:local_login_t:s15:c0.c1023 tcontext=root:sysadm_r:sysadm_t:s0-s15:c0.c1023 tclass=key permissive=1
----
time->Mon Mar 12 12:15:42 2018
type=PROCTITLE msg=audit(1520853342.035:794): proctitle=2F62696E2F6C6F67696E002D70002D2D0020202020
type=SYSCALL msg=audit(1520853342.035:794): arch=c000003e syscall=250 success=yes exit=0 a0=8 a1=fffffffc a2=fffffffd a3=0 items=0 ppid=1 pid=1427 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=ttyS0 ses=5 comm="login" exe="/usr/bin/login" subj=system_u:system_r:local_login_t:s15:c0.c1023 key=(null)
type=AVC msg=audit(1520853342.035:794): avc:  denied  { write } for  pid=1427 comm="login" scontext=system_u:system_r:local_login_t:s15:c0.c1023 tcontext=root:sysadm_r:sysadm_t:s0-s15:c0.c1023 tclass=key permissive=1
----
time->Mon Mar 12 12:15:42 2018
type=PROCTITLE msg=audit(1520853342.169:824): proctitle="(systemd)"
type=SYSCALL msg=audit(1520853342.169:824): arch=c000003e syscall=16 success=no exit=-25 a0=2 a1=5401 a2=7ffc7b944580 a3=73 items=0 ppid=1 pid=1433 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=6 comm="systemd" exe="/usr/lib/systemd/systemd" subj=root:sysadm_r:sysadm_t:s0 key=(null)
type=AVC msg=audit(1520853342.169:824): avc:  denied  { ioctl } for  pid=1433 comm="systemd" path="socket:[26548]" dev="sockfs" ino=26548 ioctlcmd=0x5401 scontext=root:sysadm_r:sysadm_t:s0 tcontext=system_u:system_r:init_t:s0-s15:c0.c1023 tclass=unix_stream_socket permissive=1
----
time->Mon Mar 12 12:15:42 2018
type=PROCTITLE msg=audit(1520853342.221:835): proctitle=2F62696E2F6C6F67696E002D70002D2D0020202020
type=SYSCALL msg=audit(1520853342.221:835): arch=c000003e syscall=47 success=yes exit=24 a0=4 a1=7ffe3dcddce0 a2=40004040 a3=0 items=0 ppid=1 pid=1427 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=ttyS0 ses=5 comm="login" exe="/usr/bin/login" subj=system_u:system_r:local_login_t:s15:c0.c1023 key=(null)
type=AVC msg=audit(1520853342.221:835): avc:  denied  { use } for  pid=1427 comm="login" path="/run/systemd/sessions/5.ref" dev="tmpfs" ino=26661 scontext=system_u:system_r:local_login_t:s15:c0.c1023 tcontext=system_u:system_r:systemd_logind_t:s0-s15:c0.c1023 tclass=fd permissive=1


or, if you prefer the audit2allow output,

#============= local_login_t ==============

#!!!! This avc is a constraint violation.  You would need to modify the attributes of either the source or target types to allow this access.
#Constraint rule: 
#       mlsconstrain key { view read write search link setattr create } ((l1 eq l2 -Fail-)  or (t1 == mlsprocwritetoclr)  and (h1 dom l2)  and (l1 domby l2 -Fail-)  or (t1 == mlsprocwrite -Fail-) ); Constraint DENIED

#       Possible cause is the source user (system_u) and target user (root) are different.
#       Possible cause is the source role (system_r) and target role (sysadm_r) are different.
#       Possible cause is the source level (s15:c0.c1023) and target level (s0-s15:c0.c1023) are different.
allow local_login_t sysadm_t:key { create write };

#!!!! This avc is a constraint violation.  You would need to modify the attributes of either the source or target types to allow this access.
#Constraint rule: 
#       mlsconstrain fd { use } ((l1 eq l2 -Fail-)  or (t1 == mlsfduse -Fail-)  or (t2 == mlsfdshare -Fail-) ); Constraint DENIED

#       Possible cause is the source level (s15:c0.c1023) and target level (s0-s15:c0.c1023) are different.
allow local_login_t systemd_logind_t:fd use;

#============= sysadm_t ==============
allow sysadm_t init_t:unix_stream_socket ioctl;

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.