Bug 827572

Summary: 389-admin - Can't call method "getText"
Product: [Fedora] Fedora Reporter: Ludovic Danigo <ldng>
Component: 389-adminAssignee: Rich Megginson <rmeggins>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: nhosoi, nkinder, rmeggins, sbrown
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 09:55:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ludovic Danigo 2012-06-01 19:11:16 UTC
Description of problem:

Falla el setup Express (2)

Are you ready to set up your servers? [yes]: 
Creating directory server . . .
Can't call method "getText" on an undefined value at /usr/lib64/dirsrv/perl/DSUtil.pm line 232, <STDIN> line 14.


Version-Release number of selected component (if applicable):
389-admin-1.1.29-1.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. run setup-ds-admin.pl
2. Select Express setup

Comment 1 Steve B 2012-06-30 08:24:03 UTC
(In reply to comment #0)
> Description of problem:

Falla el setup Express (2)

Are you ready to set up
> your servers? [yes]: 
Creating directory server . . .
Can't call method
> "getText" on an undefined value at /usr/lib64/dirsrv/perl/DSUtil.pm line
> 232, <STDIN> line 14.


Version-Release number of selected component (if
> applicable):
389-admin-1.1.29-1.fc17.x86_64

How reproducible:
always

Steps
> to Reproduce:
1. run setup-ds-admin.pl
2. Select Express setup


Hi, I had this same issue using typical installation, option [2], I found I had to add my fully qualified hostname to my hosts file, as I receieved a warning during configuration of 389-DS, after restarting and re-running the configuration it seemed to work ok,

Cheers

Steve B

Comment 2 Rich Megginson 2012-07-31 17:56:18 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/422

Comment 3 Fedora End Of Life 2013-07-04 02:59:44 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2013-08-01 09:55:42 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.