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:
Since the rebase to version 8.3.1 it is not possible to run FRR as a regular user other than root. Even though this would not make much sense when running directly in the host system, since most of the daemons won't start anyway, it makes sense for example in a container. Having a hard requirement to run stuff as root does not make much sense.

Version-Release number of selected component (if applicable):
frr-8.3.1-3.el9

How reproducible:
100%

Steps to Reproduce:
1. Create a docker file to run frr in a container:
$ cat << EOF > Dockerfile
FROM quay.io/centos/centos:stream9
RUN dnf install frr -y
EOF

2. Build the container
$ podman build . -t frr83

3. Run the content as user frr
$ podman run -it -u frr frr83 bash

4. Try to start FRR:
bash-5.1$ whoami
frr
bash-5.1$ /usr/libexec/frr/frrinit.sh start
Only users having EUID=0 can start/stop daemons
bash-5.1$ 

Actual results:
FRR not started because the EUID of the user is not that of a root.

Expected results:
This should be possible in certain use cases.

Additional info:
Originally discussed in bug #2127494.

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 (Moderate: frr security, 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/RHSA-2023:2202