Upgrade of a working domain controller failed in dogtag operations. @dmoluguw, @cipherboy, could you please investigate (look at 'Automated Tests' tab).
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.
Thanks to @cipherboy, we see that this is due to F32 beta freeze. So even though F32 pki update was created 11 days ago, it was already during the beta freeze period and it never was pushed to stable updates. The freeze period ended yesterday, thus pushing the update to stable. Now, 389-ds-base update was created before that happened, thus taking 'old' pki because that's the only set of packages available in F32.
We need to re-run tests on the 389-ds-base bodhi update.
Yeah, I was working on the same theory but our main test runner crashed before I could confirm it last night. I've added the F32 pki-base update to the 'workarounds' list for now and re-run the affected test for all affected updates, including this one, it's running or queued now.
This update has been submitted for testing by mreynolds.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Upgrade of a working domain controller failed in dogtag operations. @dmoluguw, @cipherboy, could you please investigate (look at 'Automated Tests' tab).
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.
Thanks to @cipherboy, we see that this is due to F32 beta freeze. So even though F32 pki update was created 11 days ago, it was already during the beta freeze period and it never was pushed to stable updates. The freeze period ended yesterday, thus pushing the update to stable. Now, 389-ds-base update was created before that happened, thus taking 'old' pki because that's the only set of packages available in F32.
We need to re-run tests on the 389-ds-base bodhi update.
Yeah, I was working on the same theory but our main test runner crashed before I could confirm it last night. I've added the F32 pki-base update to the 'workarounds' list for now and re-run the affected test for all affected updates, including this one, it's running or queued now.
According to the OpenQA runs, everything is green now for FreeIPA test scenarios.
This update can be pushed to stable now if the maintainer wishes
This update has been obsoleted by 389-ds-base-1.4.3.5-1.fc32.