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.
Cause: Supplying an invalid hostname to the server install script
Consequence: A vague error message is reported
Fix: Return a proper error message when the hostname is invalid
Result: A clear error message is returned when then setup script comes across an error with the hostname.
DescriptionNathanael Noblet
2013-09-26 22:52:01 UTC
Created attachment 803632[details]
Patch that fixes issue
Description of problem:
I'm trying to setup a 389 server. It is done automatically via the kolab-setup which intern is calling the 389 setup script. It fails because DSUtil.pm doesn't check if $res exists before calling functions on it.
I get the following error:
Can't call method "getText" on an undefined value at /usr/lib64/dirsrv/perl/DSUtil.pm line 259.
Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-22.el6_4.x86_64
How reproducible:
Always
Obviously this is fixed in a newer version of 389 - however the EPEL package doesn't seem to be getting updated.
The attached patch fixes the issue
I realize it was fixed in newer versions of 389-ds. However the version provided to epel is 1.2.2. So there needs to be a patch for epel or epel needs an updated version.
koji latest-pkg dist-6E-epel 389-ds
Build Tag Built by
---------------------------------------- -------------------- ----------------
389-ds-1.2.2-1.el6 dist-6E-epel rmeggins
Wrong package - you want 389-ds-base - 389-ds is just a "meta" package wrapper around the other components
Also note that 389-ds-base is not technically in EPEL6 since it is included in the base RHEL6 (or whatever EL6 distro you are using) - see http://port389.org/wiki/Download
This was fixed in 389-ds-base-1.2.11.23.
Verification steps:
[1] Run setup-ds.pl
[2] Provide an invalid hostname during the install (bogus.bogus.bogus.com)
[3] The error should not be (Can't call method "getText"), but it should instead mention the invalid hostname,
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1385.html
Created attachment 803632 [details] Patch that fixes issue Description of problem: I'm trying to setup a 389 server. It is done automatically via the kolab-setup which intern is calling the 389 setup script. It fails because DSUtil.pm doesn't check if $res exists before calling functions on it. I get the following error: Can't call method "getText" on an undefined value at /usr/lib64/dirsrv/perl/DSUtil.pm line 259. Version-Release number of selected component (if applicable): 389-ds-base-1.2.11.15-22.el6_4.x86_64 How reproducible: Always Obviously this is fixed in a newer version of 389 - however the EPEL package doesn't seem to be getting updated. The attached patch fixes the issue