Bump version to 184.108.40.206
Bump version to 220.127.116.11
Bump version to 18.104.22.168
This update has been submitted for testing by mreynolds.
This update has obsoleted 389-ds-base-22.214.171.124-1.fc27, and has inherited its bugs and notes.
This update has been pushed to testing.
This seems to cause failures in the openQA tests:
Basically it seems like user logins are failing - the 'freeipa_password_change' test module fails when trying to log into the web UI as test3, and the 'freeipa_client' test module fails when trying to log into a console as test1. Those are both user accounts created on the server after initial server deployment. It's noticeable that another test module which logs into the web UI as the admin user succeeds - that login worked.
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.
Any details as to why 389-ds-base is causing this FreeIPA WebUI problem? There have not been any changes to how passwords are changed in 389-ds-base in a very long time, and FreeIPA uses its own custom password policy plugin.
It's not a web ui problem. Note I said it also causes console login as a user to fail. It's an authentication problem, somehow. I don't have any details yet because I was at a conference and it's a bit awkward to debug, there's nothing super obvious in the logs. But the tests reliably fail with this update and pass without it, and it looks like similar failures have happened on rawhide/29 recently when the tests have actually made it this far. I'll file a bug with logs attached once I've looked into it a bit more.
Here's some circumstantial evidence, btw: the problematic update is 126.96.36.199. The equivalent release on the 1.4 branch, I think, is 188.8.131.52, those two came out at the same time. 184.108.40.206 was sent to F27 as an update candidate (this update), and 220.127.116.11 was sent to Rawhide at the time and so will be in both Rawhide and F29, but no update was sent to F28 - an F28 build was done in Koji, but no update was submitted.
This exactly matches up with what we're seeing - the bug seems to be happening in F29 and Rawhide, is happening in tests of this update (18.104.22.168) but not other F27 tests run without this update (which will be using 22.214.171.124, I think), and is not happening in any F28 tests (which will be using 126.96.36.199).
I'm gonna maybe run tests with various of the 1.3.8.* builds to try and pin down exactly when this problem appeared. From the existing openQA results it seems to have happened at least in 188.8.131.52 already; the 184.108.40.206 results are useless because server deployment failed...
The issue that IPA ran into was around unhashed passwords. It was added in 220.127.116.11, but removed in 18.104.22.168. So I'm surprised to see the same problem in 22.214.171.124. I have to assume it's "something else" that is causing the failure.
It really can't be, because the updates tests are pretty focused. They install a stable base image, then set up a repo containing only the packages from the update to be tested, then run an update, then reboot, then run the test.
So, when the tests run on this update, they have a stable base F27, plus the updated 389-ds-base package...and they fail. When the tests run on any other F27 update, they have the stable base F27, plus whatever packages were in that update...and the FreeIPA tests usually pass, for other updates. Look, here are the tests for a recent F27 kernel update - so that test will have run with the same base image, plus the updated kernel. Note the FreeIPA tests passed just fine.
Note, it seems the bug actually appeared at least as early as 126.96.36.199 - it didn't appear in 188.8.131.52. I just re-scheduled the tests for 184.108.40.206 last night, and here they are - failure in two client tests, as we've seen before, it fails on login, both to web UI and to a console. I can't tell if this bug existed in 220.127.116.11, though, as FreeIPA server deployment fails in 18.104.22.168. So the delta we know so far is: it works with 22.214.171.124 and fails with 126.96.36.199 and 188.8.131.52. It also seems that it worked with 184.108.40.206 but fails with 220.127.116.11 - I'm not sure about 18.104.22.168 yet.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
Sorry I didn't file a bug yet, btw, life keeps getting in the way :( I'll get to it tomorrow for sure...
I understand :-) Thanks!
This update has been obsoleted by 389-ds-base-22.214.171.124-1.fc27.
Comment fields support Fedora-Flavored Markdown.
Text fields in Bodhi2 support an
version of markdown.
This is a cheat sheet for your reference.
You can do headers by underlining or by prefixing with the # character:
This is an H1
This is an H2
# This is another H1
## This is another H2
You can do blockquotes using email-style prefixes with the > character:
> This is a quotation
> over many lines
> > and it can be nested(!)
Lists work like you'd expect, by prefixing with any of the *, +, or - characters:
Check out this list:
* a list..
You need a blank line between a paragraph and the start of a list for the renderer to pick up on it.
Emphasis can be added like this:
You can save your code references from being misinterpreted as emphasis by surrounding them with backtick characters (`):
Use `the_best_function()` and _not_ that crummy one.
Links look like this:
..but we also support bare links if you just provide a URL.
You can create code blocks by indenting
every line of the block by at least 4 spaces or 1 tab.
Here is a code block:
for i in range(4):
You can reference bug reports by simply writing something of the form tracker#ticketid.
This fixes PHP#1234 and Python#2345
... we will automatically generate links to the tickets in the appropriate trackers in place.
The supported bug tracker prefixes are: (these are all case-insensitive)
And you can refer to other users by prefixing their username with the @ symbol.
This will generate a link to their profile, but it won't necessarily send them a notification unless they have a special FMN rule set up to catch it.
Lastly, you can embed inline images with syntax like this:
Is the update generally functional? (karma)
You need to be logged in to add karma!
Copyright © 2007-2018 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.