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:
Upstream test test_named_conf_crypto_policy failing on RHEL


Version-Release number of selected component (if applicable):
ipa-4.9.6-1.el9


Steps to Reproduce:
1. run upstream ipatests/test_integration/test_upgrade.py::test_named_conf_crypto_policy()

Actual results:
>       assert paths.NAMED_CRYPTO_POLICY_FILE in named_conf
E       TypeError: 'in <string>' requires string as left operand, not NoneType

TypeError: 'in <string>' requires string as left operand, not NoneType

NAMED_CRYPTO_POLICY_FILE constant defined in 'fedora' backend needs to be propagated to 'rhel' backend as we have the same crypto-policies there in RHEL 8.4+

Upstream ticket:
https://pagure.io/freeipa/issue/8925

Fixed upstream
master:
https://pagure.io/freeipa/c/178fb134fb4f4f465376020292f111a7aa099f30

Fixed upstream
ipa-4-9:
https://pagure.io/freeipa/c/1a5159b216455070eb51b6a11ceaf0033fc8ce4c

Test( test_named_conf_crypto_policy ) is executed and successful in nightly, based on this info moving it to verified

snip from automation log files:

(1) test-result.txt.gz

============================= test session starts ==============================
platform linux -- Python 3.9.6, pytest-6.2.2, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3
cachedir: /home/cloud-user/.pytest_cache
collecting ... collected 9 items

test_integration/test_upgrade.py::TestUpgrade::test_named_conf_crypto_policy PASSED [ 33%]

(2) runner.log 

2021-07-29T06:59:45+0000 ok: [master.testrelm.test] => (item=ipa-server) => 
2021-07-29T06:59:45+0000   msg:
2021-07-29T06:59:45+0000   - arch: x86_64
2021-07-29T06:59:45+0000     epoch: null
2021-07-29T06:59:45+0000     name: ipa-server
2021-07-29T06:59:45+0000     release: 4.el9
2021-07-29T06:59:45+0000     source: rpm
2021-07-29T06:59:45+0000     version: 4.9.6