We stuck to the guide on https://directory.fedoraproject.org/docs/389ds/howto/howto-deploy-389ds-on-openshift.html but tried to leave out LDAPs and all the certificate stuff for now. Pod is starting but crashes immediately with the following error:
kubectl logs dirsrv-0 dirsrv-container -n dirsrv-dev
INFO: The 389 Directory Server Container Bootstrap
INFO: Inspired by works of: ITS, The University of Adelaide
INFO: 389 Directory Server Version: 2.2.2
INFO: Initialising 389-ds-container due to empty volume ...
DEBUG: Running setup with verbose
DEBUG: START: Starting installation ...
DEBUG: READY: Preparing installation for localhost...
INFO: Validate installation settings ...
DEBUG: PASSED: using config settings 999999999
DEBUG: PASSED: user / group checking
DEBUG: PASSED: prefix checking
Traceback (most recent call last):
File "/usr/lib/dirsrv/dscontainer", line 467, in <module>
begin_magic()
File "/usr/lib/dirsrv/dscontainer", line 270, in begin_magic
if not sds.create_from_args(g2b.collect(), s2b.collect()):
File "/usr/lib/python3.10/site-packages/lib389/instance/setup.py", line 685, in create_from_args
self._prepare_ds(general, slapd, backends)
File "/usr/lib/python3.10/site-packages/lib389/instance/setup.py", line 612, in _prepare_ds
assert_c(len(insts) == 0, "Another instance named '%s' may already exist" % slapd['instance_name'])
File "/usr/lib/python3.10/site-packages/lib389/utils.py", line 1274, in assert_c
raise AssertionError(msg)
AssertionError: Another instance named 'localhost' may already exist
Any idea why?
Cheers,
Ronald
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No comments:
Post a Comment