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.
.Changing a security parameter now works correctly
Previously, when you changed a security parameter by using the `dsconf __instance_name__ security set` command, the operation failed with the error:
----
Name 'log' is not defined
----
With this update, the security parameter change works as expected.
Description of problem:
Trying to change a security parameter ends with the error: name 'log' is not defined
# dsconf -v slapd-EXAMPLE-TEST security set --tls-protocol-min=TLS1.0
DEBUG: The 389 Directory Server Configuration Tool
DEBUG: Inspired by works of: ITS, The University of Adelaide
DEBUG: dsrc path: /root/.dsrc
DEBUG: dsrc container path: /data/config/container.inf
DEBUG: dsrc instances: []
DEBUG: dsrc no such section: slapd-EXAMPLE-TEST
DEBUG: Called with: Namespace(instance='slapd-EXAMPLE-TEST', verbose=True, binddn=None, bindpw=None, prompt=False, pwdfile=None, basedn=None, starttls=False, json=False, security=None, listen_host=None, secure_port=None, tls_client_auth=None, tls_client_renegotiation=None, require_secure_authentication=None, check_hostname=None, verify_cert_chain_on_startup=None, session_timeout=None, tls_protocol_min='TLS1.0', tls_protocol_max=None, allow_insecure_ciphers=None, allow_weak_dh_param=None, cipher_pref=None, func=<function _security_generic_set_parser.<locals>.<lambda> at 0x7fec1abd85e0>)
DEBUG: Instance details: {'uri': 'slapd-EXAMPLE-TEST', 'basedn': None, 'binddn': None, 'bindpw': None, 'saslmech': None, 'tls_cacertdir': None, 'tls_cert': None, 'tls_key': None, 'tls_reqcert': None, 'starttls': False, 'prompt': False, 'pwdfile': None, 'args': {'ldapurl': 'slapd-EXAMPLE-TEST', 'root-dn': None}}
DEBUG: Allocate <class 'lib389.DirSrv'> with ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None
DEBUG: Allocate <class 'lib389.DirSrv'> with ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None
DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None
DEBUG: open(): Connecting to uri ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket
DEBUG: Using dirsrv ca certificate /etc/dirsrv/slapd-EXAMPLE-TEST
DEBUG: Using external ca certificate /etc/dirsrv/slapd-EXAMPLE-TEST
DEBUG: Using /etc/openldap/ldap.conf certificate policy
DEBUG: ldap.OPT_X_TLS_REQUIRE_CERT = 2
DEBUG: open(): Using root autobind ...
DEBUG: open(): bound as None
DEBUG: Retrieving entry with [('',)]
DEBUG: Retrieved entry [dn:
vendorVersion: 389-Directory/2.2.4 B2022.347.0000
]
DEBUG: cn=encryption,cn=config set REPLACE: ('sslVersionMin', 'TLS1.0')
DEBUG: name 'log' is not defined
Traceback (most recent call last):
File "/usr/sbin/dsconf", line 138, in <module>
result = args.func(inst, None, log, args)
File "/usr/lib/python3.9/site-packages/lib389/cli_conf/security.py", line 113, in <lambda>
p.set_defaults(func=lambda *args: _security_generic_set(*args, attrs_map))
File "/usr/lib/python3.9/site-packages/lib389/cli_conf/security.py", line 102, in _security_generic_set
log.info(f"Successfully updated security configuration ({props.attr})")
NameError: name 'log' is not defined
ERROR: Error: name 'log' is not defined
Version-Release number of selected component (if applicable):
389-ds-base-2.2.4-3.el9.x86_64
How reproducible:
Every time. It does successfully update dse.ldif.
Steps to Reproduce:
1. I found it after installing IPA
2. dsconf -v slapd-EXAMPLE-TEST security set --tls-protocol-min=TLS1.0
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 (389-ds-base 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-2023:6350
Description of problem: Trying to change a security parameter ends with the error: name 'log' is not defined # dsconf -v slapd-EXAMPLE-TEST security set --tls-protocol-min=TLS1.0 DEBUG: The 389 Directory Server Configuration Tool DEBUG: Inspired by works of: ITS, The University of Adelaide DEBUG: dsrc path: /root/.dsrc DEBUG: dsrc container path: /data/config/container.inf DEBUG: dsrc instances: [] DEBUG: dsrc no such section: slapd-EXAMPLE-TEST DEBUG: Called with: Namespace(instance='slapd-EXAMPLE-TEST', verbose=True, binddn=None, bindpw=None, prompt=False, pwdfile=None, basedn=None, starttls=False, json=False, security=None, listen_host=None, secure_port=None, tls_client_auth=None, tls_client_renegotiation=None, require_secure_authentication=None, check_hostname=None, verify_cert_chain_on_startup=None, session_timeout=None, tls_protocol_min='TLS1.0', tls_protocol_max=None, allow_insecure_ciphers=None, allow_weak_dh_param=None, cipher_pref=None, func=<function _security_generic_set_parser.<locals>.<lambda> at 0x7fec1abd85e0>) DEBUG: Instance details: {'uri': 'slapd-EXAMPLE-TEST', 'basedn': None, 'binddn': None, 'bindpw': None, 'saslmech': None, 'tls_cacertdir': None, 'tls_cert': None, 'tls_key': None, 'tls_reqcert': None, 'starttls': False, 'prompt': False, 'pwdfile': None, 'args': {'ldapurl': 'slapd-EXAMPLE-TEST', 'root-dn': None}} DEBUG: Allocate <class 'lib389.DirSrv'> with ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None DEBUG: Allocate <class 'lib389.DirSrv'> with ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None DEBUG: Allocate <class 'lib389.DirSrv'> with %2frun%2fslapd-EXAMPLE-TEST.socket:None DEBUG: open(): Connecting to uri ldapi://%2frun%2fslapd-EXAMPLE-TEST.socket DEBUG: Using dirsrv ca certificate /etc/dirsrv/slapd-EXAMPLE-TEST DEBUG: Using external ca certificate /etc/dirsrv/slapd-EXAMPLE-TEST DEBUG: Using /etc/openldap/ldap.conf certificate policy DEBUG: ldap.OPT_X_TLS_REQUIRE_CERT = 2 DEBUG: open(): Using root autobind ... DEBUG: open(): bound as None DEBUG: Retrieving entry with [('',)] DEBUG: Retrieved entry [dn: vendorVersion: 389-Directory/2.2.4 B2022.347.0000 ] DEBUG: cn=encryption,cn=config set REPLACE: ('sslVersionMin', 'TLS1.0') DEBUG: name 'log' is not defined Traceback (most recent call last): File "/usr/sbin/dsconf", line 138, in <module> result = args.func(inst, None, log, args) File "/usr/lib/python3.9/site-packages/lib389/cli_conf/security.py", line 113, in <lambda> p.set_defaults(func=lambda *args: _security_generic_set(*args, attrs_map)) File "/usr/lib/python3.9/site-packages/lib389/cli_conf/security.py", line 102, in _security_generic_set log.info(f"Successfully updated security configuration ({props.attr})") NameError: name 'log' is not defined ERROR: Error: name 'log' is not defined Version-Release number of selected component (if applicable): 389-ds-base-2.2.4-3.el9.x86_64 How reproducible: Every time. It does successfully update dse.ldif. Steps to Reproduce: 1. I found it after installing IPA 2. dsconf -v slapd-EXAMPLE-TEST security set --tls-protocol-min=TLS1.0