#3016 pki-tools cannot be installed on current Rawhide (due to tomcat version bump)
Closed: fixed Opened by mharmsen.

tomcat was recently bumped to 9.0 in Rawhide:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1078072

it now provides tomcat-servlet-4.0-api , not tomcat-servlet-3.1-api . But pki-core has not been updated for this change: pki-tools still requires tomcat-servlet-3.1-api . As a result, pki-tools cannot be installed, which means pki-server cannot be installed, which means freeipa-server cannot be installed, which means FreeIPA doesn't work.

This is a clear Beta blocker, per Basic criterion "Release-blocking roles and the supported role configuration interfaces must meet the core functional Role Definition Requirements to the extent that supported roles can be successfully deployed, started, stopped, brought to a working configuration, and queried", as 'domain controller' is a release-blocking role.


Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1574711
- Custom field type adjusted to None
- Custom field version adjusted to None

Fixed in master branch:

  • https://github.com/dogtagpki/pki/commit/ed08e351619f10a0ab93fd8ad7937b5f4002b985
  • https://github.com/dogtagpki/pki/commit/7b9aa323ed34f9653baac4d77a838cab0fa06c07

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.1 (was: 10.6)
- Issue status updated to: Closed (was: Open)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3134

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, and we apologize for any inconvenience.

Metadata