Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I have problem with these two cases:
1) /usr/bin/radtest -x -4 testuser RedHat localhost:1812 1812 RedHat -1 localhost | grep -q 'PPP'
2) /usr/bin/radtest -x -4 testuser RedHat localhost:1812 1812 RedHat YES localhost | grep -q 'PPP'
Return code 1 is expected for these cases in our tests. Currently these commands return 0.
radtest was patched by us to handle the PPPhint, our logic said truth was any positive integer. Upstream did not implement the same logic when then fixed radtest, instead upstream implemented truth as any argument which is non-zero. This is why the last two tests were failing, it was expecting -1 and YES to disable the PPPhint but because the test is anything which is non-zero these arguments enable PPPhint. This behaviour changed I believe with freeradius 2.2.3 (not positive).
There were also several problems with the script which I had to fix in addition.
* The shared secret was not updated in the radius config to RedHat, the default is testing123. Therefore the shared secret of RedHat was changed to testing123.
* The users file was not updated with the test user and password. Now the users file is backed up and a user named "testuser" with a password of "RedHat" is created as per the test expectations.
* The radius server was not started nor was it restarted after updating the users file with the testuer, now the daemon is managed in the script (using the newly introduced RadiusdStart and RadiusdStop functions.
Closing this as NOTABUG because we'll follow upstream and all the issues are really in the test script. I will attach the version of runtest I updated to bug #1021541 where we're tracking the test updated for FreeRADIUS 3.