[2277] in Kerberos-V5-bugs
krb5-admin/46: kadm5 sapi.2 unit test fails 104/105
daemon@ATHENA.MIT.EDU (epeisach@MIT.EDU)
Tue Oct 1 12:10:16 1996
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: bjaspan@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, epeisach@MIT.EDU
Date: Tue, 1 Oct 1996 12:08:07 -0400
From: epeisach@MIT.EDU
Reply-To: epeisach@MIT.EDU
To: krb5-bugs@MIT.EDU
>Number: 46
>Category: krb5-admin
>Synopsis: kadm5 sapi.2 unit test fails 104/105
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bjaspan
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Oct e 12:09:00 EDT 1996
>Last-Modified:
>Originator: Ezra Peisach
>Organization:
mit
>Release: 1.0-development
>Environment:
System: OSF1 kangaroo.mit.edu V3.2 214 alpha
Machine: alpha
>Description:
The kadm5 server unit tests fails in init-v2.exp tests 104 and
105. These are related to the ADB name and lock file.
>How-To-Repeat:
gmake check
>Fix:
in kadm5/alt_prof.c the stanza at KADM5_CONFIG_ADBNAME (line 376).
a) KADM5_CONFIG_ADBNAME is using a name based upon the dbname. You
cannot pass in a name to use - the dbname is used as the basis...
b) The tests try setting KADM5_CONFIG-ADBNAME and
KADM5_CONFIG_ADB_LOCKFILE. The lockfile optoin is ignored - you cannot
specify it. The config_adbname is essentially ignored as well...
c) There is a bug - if my params.mask contains KADM5_CONFIG_ADBNAME, but
not KADM5_CONFIG_DBNAME, the admin_dbname would not be set properly..
Fixes:
a & b) I believe tests 104 and 105 should be removed from the test suite. They
are no longer relevant.
c) params.admin_dbname needs to be set if KADM5_CONFIG_DBNAME or
KADM5_CONFIG_ADBNAME is set.
>Audit-Trail:
>Unformatted:
kadm5 sapi tests fail 104/105
