On prefix deployment, the installation directory belongs to the local user not 'dirsrv'. In addition user running the instance is not 'root', it should not try to label ports or run semanage.
1.4.0
It fails to create the instances
it should succeeds
and there is another issue, if creating the instance fails it is removed independenly of the DEBUGGING set:
try: self._install_ds(general, slapd, backends) except ValueError as e: self.log.fatal("Error: " + str(e) + ", removing incomplete installation...") self._remove_failed_install(slapd['instance_name'])
which makes it hard to debug setup failures
Metadata Update from @lkrispen: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Isn't the debugging removal dependent on the individual test case? For most tests it comes from the topology fixture, but some older tests intercept and do this themself. Is there a specific test case where you see these error?
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
https://pagure.io/389-ds-base/pull-request/50448
Metadata Update from @mreynolds: - Issue assigned to tbordaz - Issue priority set to: normal - Issue set to the milestone: 1.4.3 (was: 1.4.0)
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/3356
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.