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:

When update-crypto-policies --set is invoked without a parameter to --set option, current policy should be set. Instead, endless loop is entered.

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

crypto-policies-20181122-1.git93661f7.el8.noarch

How reproducible:

Always

Steps to Reproduce:

0. update-crypto-policies --set DEFAULT
1. update-crypto-policies --set
2. update-crypto-policies --show

Actual results:

1. Setting system policy to DEFAULT
2. (endless loop)

Expected results:

1. Setting system policy to DEFAULT
2. Setting system policy to DEFAULT
3. DEFAULT

Additional info:

    bash -x update-crypto-policies --set
     
    + umask 022
    + : /usr/share/crypto-policies
    + : /etc/crypto-policies
    + local_dir=/etc/crypto-policies/local.d
    + backend_config_dir=/etc/crypto-policies/back-ends
    + state_dir=/etc/crypto-policies/state
    + errcode=0
    + nocheck=0
    + noreload=0
    + profile=
    + test 1 -ge 1
    + case "$1" in
    + profile=
    + shift 2
    + test 1 -ge 1
    + case "$1" in
    + profile=
    + shift 2
    + test 1 -ge 1
    + case "$1" in
    + profile=
    + ....

Acceptance Criteria:
 
 * When update-crypto-policies --set is used without parameters, current policy is set.

Successfully verified on all supported architectures.

NEW (crypto-policies-20181217-1.git9a35207.el8)
===============================================
:: [  BEGIN   ] :: Running 'update-crypto-policies --set'
Setting system policy to DEFAULT
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
:: [   PASS   ] :: Command 'update-crypto-policies --set' (Expected 0, got 0)
:: [  BEGIN   ] :: Running 'update-crypto-policies --show | grep DEFAULT'
DEFAULT
:: [   PASS   ] :: Command 'update-crypto-policies --show | grep DEFAULT' (Expected 0, got 0)

See TJ#3239263 for more details.