New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prefixdir in config.log set to 'NONE' #2283
Comments
Comment from firstyear (@Firstyear) at 2017-04-20 05:45:14 Metadata Update from @Firstyear:
|
Comment from firstyear (@Firstyear) at 2017-04-20 06:03:25 |
Comment from firstyear (@Firstyear) at 2017-04-20 06:03:30 Metadata Update from @Firstyear:
|
Comment from ilias95 (@ilstam) at 2017-04-20 12:29:18 I applied the patch, rebuilt the server and the issue seems to has been fixed. Now, I have a valid value for prefixdir in my config.log and the related test cases in lib389 pass. |
Comment from mreynolds (@mreynolds389) at 2017-04-21 14:29:13 Metadata Update from @mreynolds389:
|
Comment from firstyear (@Firstyear) at 2017-04-24 01:24:51 commit b393875 Thanks for finding this! |
Comment from firstyear (@Firstyear) at 2017-04-24 01:24:55 Metadata Update from @Firstyear:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49224
Issue Description
prefixdir in my config.log is set to 'NONE'. So the corresponding value in defaults.inf is also invalid. This causes the following assertion in lib389 to fail (and as a result a lot of the tests too): https://pagure.io/lib389/blob/master/f/lib389/instance/setup.py#_221
Package Version and Platform
git master on Fedora 25
Steps to reproduce
I just run the following:
I don't know if it's easy to reproduce though.
Actual results
In my config.log:
prefix='/opt/dirsrv'
prefixdir='NONE'
Expected results
prefix='/opt/dirsrv'
prefixdir='/opt/dirsrv'
The text was updated successfully, but these errors were encountered: