#50741 bdb_start - Detected Disorderly Shutdown last time Directory Server was running
Closed: wontfix by mreynolds. Opened by tbordaz.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1773115

Description of problem:
In a lot of test cases I see the following error in the logs:
NOTICE - bdb_start - Detected Disorderly Shutdown last time Directory Server
was running
Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.4-3.module+el8.2.0+4718+1b57dca2.x86_64.rpm
How reproducible:
always
Steps to Reproduce:
1. Run tests/suites/plugins/acceptance_test.py
2.
3.
Actual results:
The error about disorderly shutdown is logged
Expected results:
There shouldn't be a disorderly shutdown.
Additional info:

Metadata Update from @tbordaz:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1773115

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

PR https://pagure.io/389-ds-base/pull-request/50743

Metadata Update from @tbordaz:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Pushed upstream.

The following tests are still failing:

suites/import/regression_test.py::test_del_suffix_backend FAILED         [ 72%]
suites/replication/cleanallruv_test.py::test_clean_restart FAILED        [ 90%]
suites/replication/cleanallruv_test.py::test_abort_restart FAILED        [ 90%]
suites/replication/cleanallruv_test.py::test_clean_shutdown_crash FAILED [ 91%]

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.2 (was: 0.0 NEEDS_TRIAGE)

According to BZ update, those failing tests (regression/cleanallruv) are fixed with https://pagure.io/389-ds-base/pull-request/50783

but this is not yet merged, there is an open question about function=20
naming, raised by TB :-)

On 01/23/2020 09:59 AM, thierry bordaz wrote:

tbordaz added a new comment to an issue you are following:
According to BZ update, those failing tests (regression/cleanallruv) are = fixed with https://pagure.io/389-ds-base/pull-request/50783

To reply, visit the link below or just reply to this email
https://pagure.io/389-ds-base/issue/50741

--=20
Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn,
Handelsregister: Amtsgericht M=C3=BCnchen, HRB 153243,
Gesch=C3=A4ftsf=C3=BChrer: Charles Cachera, Laurie Krebs, Michael O'Neill, =
Thomas Savage

@lkrispen please consider my comment as minor comment. It should not delay the merge.
Sorry for the noise

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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/3796

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata