bugfix update in Fedora 26 for 389-ds-base

Status: obsolete

Bump version to

Comments 7

This update has been submitted for testing by mreynolds.

This update has been pushed to testing.

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes

@sgallagh alerted me to this update possibly being broken, so I manually triggered openQA tests for it, and indeed they confirm that FreeIPA server deployment is broken with this 389-ds. It seems the CA server never comes up fully working; the deployment process tries for a long time to reach it, getting a 500 error response every time, and eventually gives up and fails. The tomcat logs show it failing to connect to the directory server with 'connection refused'. https://openqa.fedoraproject.org/tests/86992

karma: -1

This update has been obsoleted.

Add Comment & Feedback
Toggle Preview

Comment fields support Fedora-Flavored Markdown. Comments are governed under this privacy policy.

-1 0 +1 Feedback Guidelines
Test Case 389 ds base setup testcase
Test Case Create normalized dn cache testcase
Test Case Create normalized dn cache testcase2
Is the update generally functional?
Content Type
Test Gating Status
Tests not running
Submitted by
Update Type
stable threshold: 1
unstable threshold: -1
submitted a year ago
in testing a year ago

Automated Test Results

Test results and gating status may sometimes conflict as the gating status is retrieved periodically by Bodhi's backend server, while the test results presented here are retrieved upon page load. If your update is marked as gated while all the tests show green/passed, the next check of gating status should open the gate.