Bump version to 2.0.5

How to install

sudo dnf upgrade --advisory=FEDORA-2021-234a7eff94

This update has been submitted for testing by mreynolds.

3 weeks ago

This update's test gating status has been changed to 'ignored'.

3 weeks ago

This update's test gating status has been changed to 'waiting'.

3 weeks ago

This update's test gating status has been changed to 'ignored'.

3 weeks ago

This update has been pushed to testing.

3 weeks ago
User Icon abbra commented & provided feedback 3 weeks ago
karma

This build broke IPA installation. Sadly, I cannot detect what's wrong but the difference between a 389-ds-base-2.0.4-4.fc35.x86_64 and this one is a failure to start IPA topology plugin after a first restart of 389-ds instance during the installation:

May 30 12:20:08 ipa001 ns-slapd[5896]: [30/May/2021:12:20:08.166026321 -0400] - ERR - plugin_dependency_startall - Failed to resolve plugin dependencies
May 30 12:20:08 ipa001 ns-slapd[5896]: [30/May/2021:12:20:08.166586517 -0400] - ERR - plugin_dependency_startall - object plugin IPA Topology Configuration is not started

these error messages do not exist in the successful run with 2.0.4-4 as can be seen in upstream nightly runs against rawhide done just a day before this update: http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/1dc5af3e-c077-11eb-b9ba-525400550390/results.html (remote results.html to see the logs for individual tests).

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.

3 weeks ago

Sorry, this was supposed to go to rawhide's build but it is the same with the previous F34 build 389-ds-base-2.0.3-3.fc34.x86_64. A corresponding upstream CI run against F34 succeeded before this update: http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/6a3d4b16-c017-11eb-a254-fa163e2b0c01/results.html (remove results.html to see the logs for individual tests)

So, this doesn't get auto-gated because it's not critpath. But maybe we should configure a package-level gating policy for the freeipa-related packages that openQA is allowlisted to test? I can send some PRs for that...

May be. Ideally, this kind of change needs to be combined with freeipa update. I can get this done once https://github.com/freeipa/freeipa/pull/5798 is accepted and we release 4.9.4.

abbra edited this update.

New build(s):

  • freeipa-4.9.3-3.fc34

Karma has been reset.

2 weeks ago

This update has been submitted for testing by abbra.

2 weeks ago

I added a patch to handle replication plugin rename on IPA side. This should retrigger OpenQA tests.

abbra edited this update.

New build(s):

  • freeipa-4.9.3-4.fc34

Removed build(s):

  • freeipa-4.9.3-3.fc34

Karma has been reset.

2 weeks ago

With freeipa-4.9.3-4.fc34 all IPA-related tests succeeded, including upgrade from F33 to F34

This update has been pushed to testing.

2 weeks ago
User Icon frenaud commented & provided feedback 2 weeks ago
karma

Test single server installation and upgrade, works well.

This update can be pushed to stable now if the maintainer wishes

2 weeks ago

This update has been submitted for stable by abbra.

2 weeks ago

This update has been pushed to stable.

2 weeks ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-1
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
3 weeks ago
in testing
2 weeks ago
in stable
2 weeks ago
modified
2 weeks ago

Automated Test Results