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.
Description of problem:
On RHEL-9.1 'dscreate create-template' produces empty template.
Version-Release number of selected component (if applicable):
389-ds-base-2.1.3-3.el9
How reproducible:
100%
Steps to Reproduce:
1. dscreate --verbose create-template
Actual results:
# dscreate --verbose create-template
DEBUG: The 389 Directory Server Creation Tool
DEBUG: Inspired by works of: ITS, The University of Adelaide
DEBUG: Called with: Namespace(verbose=True, json=False, advanced=False, template_file='None', func=<function instance_example at 0x7fd4a9478b80>)
#
Expected results:
# dscreate --verbose create-template
DEBUG: The 389 Directory Server Creation Tool
DEBUG: Inspired by works of: ITS, The University of Adelaide
DEBUG: Called with: Namespace(verbose=True, json=False, advanced=False, template_file=None, func=<function instance_example at 0x7ffad629df70>)
;
; This is a version 2 ds setup inf file.
; It is used by the python versions of setup-ds-*
; Most options map 1 to 1 to the original .inf file.
; However, there are some differences that I envision
; For example, note the split backend section.
; You should be able to create, one, many or no backends in an install
;
; The special value {instance_name} is substituted at installation time.
;
; By default, all configuration parameters in this file are commented out.
; To use an INF file with dscreate, you must at least set the parameters
; flagged with [REQUIRED].
...
#
Additional info:
Worked fine with 389-ds-base-2.0.14-1.el9. Notice the slight difference in DEBUG lines between actual and expected results.
Description of problem: On RHEL-9.1 'dscreate create-template' produces empty template. Version-Release number of selected component (if applicable): 389-ds-base-2.1.3-3.el9 How reproducible: 100% Steps to Reproduce: 1. dscreate --verbose create-template Actual results: # dscreate --verbose create-template DEBUG: The 389 Directory Server Creation Tool DEBUG: Inspired by works of: ITS, The University of Adelaide DEBUG: Called with: Namespace(verbose=True, json=False, advanced=False, template_file='None', func=<function instance_example at 0x7fd4a9478b80>) # Expected results: # dscreate --verbose create-template DEBUG: The 389 Directory Server Creation Tool DEBUG: Inspired by works of: ITS, The University of Adelaide DEBUG: Called with: Namespace(verbose=True, json=False, advanced=False, template_file=None, func=<function instance_example at 0x7ffad629df70>) ; ; This is a version 2 ds setup inf file. ; It is used by the python versions of setup-ds-* ; Most options map 1 to 1 to the original .inf file. ; However, there are some differences that I envision ; For example, note the split backend section. ; You should be able to create, one, many or no backends in an install ; ; The special value {instance_name} is substituted at installation time. ; ; By default, all configuration parameters in this file are commented out. ; To use an INF file with dscreate, you must at least set the parameters ; flagged with [REQUIRED]. ... # Additional info: Worked fine with 389-ds-base-2.0.14-1.el9. Notice the slight difference in DEBUG lines between actual and expected results.