When upgrading from using mod_nss to mod_ssl the method disable_nss_conf() is used to delete nss.conf.
This is incorrect. Removing the file completely will cause rpm to create a new nss.conf if/when mod_nss is upgraded which will blow up an upgrade.
A zero-length or commented-version of the file should be created.
Seen by Martin Kosek while trying to upgrade the public demo.
The root of the problem is that mod_nss uses 8443 as its listener by default which is also used by dogtag.
Metadata Update from @cheimes: - Issue priority set to: critical - Issue set to the milestone: FreeIPA 4.7.2 - Issue tagged with: easyfix
Metadata Update from @okozlov: - Issue assigned to okozlov
master:
ipa-4-7:
Fixed. Instead of removing nss.conf will be replaced with an empty file, it avoids recreation in case mod_nss is reinstalled.
mod_nss
Metadata Update from @okozlov: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)