Red Hat Bugzilla – Bug 968906
upgrade 3.2_pre-relase->3.2 pki artifacts are reset to relative paths
Last modified: 2016-02-10 14:35:15 EST
There is a bug in engine-config that existed since beginning of time, it does not take the CABaseDirectory into account.
However, both the setup and the upgrade set full path for all pki artifacts, this is why this bug has been never discovered.
The database upgrade script puts two values per default, these are relative:
When system is upgraded from 3.1, after database upgrade the engine-upgrade script will convert keys to PKCS#12 format, and overwrite database settings.
However, if you upgrade from 3.2 to 3.2, then the engine-upgrade script does not overwrite the setting, leaving relative paths.
Modify keystoreUrl and truststoreUrl within database to absolute paths.
moving to modified for 3.3, as issue shouldn't happen.
is5. verified. pki settings moved into configuration
Closing - RHEV 3.3 Released