set default ticket origin to Community

Added initial screened field value.

I tried to duplicate the problem, but I could not.

Based upon the bug report:

Can't call method "getText" on an undefined value at
/usr/lib64/dirsrv/perl/DSUtil.pm line 232, <STDIN> line 14.

Line 232 is for 'warning_no_such_hostname'.
231 if ($err) {
232 return $res->getText('warning_no_such_hostname', $hn);
233 }

In setup-ds.res,
warning_no_such_hostname = Could not find an address for hostname '%s'.\n

My build is from 1.3.0, and I tested it on f17.
I ran setup-ds-admin.pl -s -f /path/to/inffile.
And the error message is printed as expected...
WARNING: There are problems with the hostname.
Could not find an address for hostname '<...>'.

The error message means that $res is not set (that it is undefined). I guess the next step would be to see where checkHostname is called, and how/why $res could be unset in those places. I see this:

DSCreate.pm.in:153
{{{
my $str = checkHostname($inf->{General}->{FullMachineName});
}}}
This does not have the $res parameter.

Updating the summary since this is not a bug in 389-admin, but in the admin script in 389-ds-base.

Bug description: If a hostname which has no corresponding IP
address associated is given to the setup-ds-admin.pl or
setup-ds.pl (e.g., bogus.bogus.bogus.com), then DSUtil.pm
complains with "Can't call method "getText" on an undefined
value".

Fix description: There were 2 missing checks in perl subroutine
checkHostname in DSUtil.pm whether the dialog resource is given
or not.

git patch file (master)
0001-Ticket-422-389-ds-base-Can-t-call-method-getText.patch

This is a bit tricky, because checkHostname is called from two completely different contexts. When called from SetupDialogs, it will have a $res that can call getText to get a localized string. But when called from sanityCheckParams, there is no $res. It should instead return a list that will eventually be used with getText. For example, we should really do something like this:
{{{
...
if ($res) {
return $res->getText('warning_hostname_not_fully_qualified', $hn);
} else {
return ('warning_hostname_not_fully_qualified', $hn);
}
...
if ($err) {
if ($res) {
return $res->getText('warning_no_such_hostname', $hn);
} else {
return ('warning_no_such_hostname', $hn);
}
}
...
}}}
etc. If $res, return a string returned by $res->getText, otherwise, return a list that will eventually be passed to $res->getText at a higher level.

This also means sanityCheckParams will need to change:
{{{
if (@errs = checkHostname($inf->{General}->{FullMachineName}, 0)) {
debug(1, @errs);
return @errs;
}

return ();

}}}

Bug description: If a hostname which has no corresponding IP
address associated is given to the setup-ds-admin.pl or
setup-ds.pl (e.g., bogus.bogus.bogus.com), then DSUtil.pm
complains with "Can't call method "getText" on an undefined
value".

Fix description: Thanks to Rich for his comments. Following
his suggestions, this patch prepares 2 different return types
in checkHostname depending upon the existence of the resource
object. If the resource is given, the subroutine returns the
error message. Otherwise, it returns the array of error message.

revised git patch file (master)
0001-Ticket-422-389-ds-base-Can-t-call-method-getText.2.patch

Reviewed by Rich and Mark (Thank you!!!)

Pushed to master: commit d8cdb35

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1012699 (''Fedora EPEL'')

To ssh://git.fedorahosted.org/git/389/ds.git
63274be..87a069c 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 87a069c
Author: Noriko Hosoi nhosoi@redhat.com
Date: Fri Dec 21 10:31:24 2012 -0800
aa19f9a..82a50df 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit 82a50df
Author: Noriko Hosoi nhosoi@redhat.com
Date: Fri Dec 21 10:31:24 2012 -0800

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/422

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.