RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Polyinstanciation template /etc/security/namespace.conf defines /var/tmp/tmp-inst as root directory for /var/tmp instances:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
/var/tmp /var/tmp/tmp-inst/   	level      root,adm
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

The database however defines /var/tmp-inst, which ends up having /var/tmp/tmp-inst unlabelled, preventing users from logging in:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
/var/tmp-inst                                      directory          system_u:object_r:tmp_t:s0 
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Please adjust to /var/tmp/tmp-inst


Version-Release number of selected component (if applicable):

selinux-policy-3.14.3-54.el8.noarch


How reproducible:

N/A

*** Bug 1934444 has been marked as a duplicate of this bug. ***

I've submitted a Fedora PR to address the issue:
https://github.com/fedora-selinux/selinux-policy/pull/683

Merged in rawhide:
commit 3ca065eef7990b37d4b57218ada8dea8f0b18580
Author: Zdenek Pytela <zpytela>
Date:   Tue Apr 6 19:53:29 2021 +0200

    Add file context specification for /var/tmp/tmp-inst

    The pam_namespace.so module allows setup of private namespaces with
    polyinstantiated directories. Directories can be polyinstantiated based
    on user name or, in the case of SELinux, user name, sensitivity level or
    complete security context.

    Previously, file context specification for /var/tmp-inst was defined
    in SELinux policy instead of /var/tmp/tmp-inst, although pam_namespace
    is pre-configured for using /var/tmp/tmp-inst. It is noted in the
    /etc/security/namespace.conf file as well as in documentation.

    Resolves: rhbz#1919253

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4420