#2844 TPS CS.cfg should be reflected with the changes after an in-place upgrade
Closed: fixed 7 years ago Opened 7 years ago by mharmsen.

TPS CS.cfg should be reflected with the changes after an in-place upgrade.

Steps to Reproduce:

New profile externalRegISEToken was introduced in CS9.2z which is not added
to TPS CS.cfg after an in-place upgrade from CS 9.2 to z-stream packages.

Workaround:

Add them manually.

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=1501436
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: critical
- Issue set to the milestone: 10.5

7 years ago

[20171025] - edewata - needed for upgrade

Metadata Update from @mharmsen:
- Issue assigned to jmagne

7 years ago

Checkins:

commit fbe1796db19693e4d5bfd2a3ef1f813558daed34 (HEAD -> DOGTAG_10_5_BRANCH, origin/DOGTAG_10_5_BRANCH, gerrit/DOGTAG_10_5_BRANCH)
Author: Jack Magne jmagne@redhat.com
Date: Wed Jan 24 18:51:11 2018 -0800

Fix Bug 1501436 - TPS CS.cfg should be reflected with the changes after an in-place upgrade.
Spec file changes only for the main commit that fixes this bug.

Change-Id: Id5898b719afd75dff9701d7c7e7906e0a3e6147c

commit bf199fa8b2215d68765117b79626a72374d71981
Author: Jack Magne jmagne@redhat.com
Date: Tue Jan 23 18:31:53 2018 -0800

Fix Bug 1501436 - TPS CS.cfg should be reflected with the changes after an in-place upgrade.

This upgrade script will add the needed config params to an existing CS.cfg for TPS.

The params consist of the params required for the token profile : externalRegISEtoken.

The code also grabs the unsecure phone home url out of the instances's server.xml.
This way the new profile is configured exactly like what happens when doing a pkispawn.
The correct nonsecure url will be in place.

Added some review changes. Also we modified the python properties file class to be able to
handle a property value that happens to contain the delimeter "=". Ex name=cn=people.

Added directory server/upgrade/10.5.1 so rhel can use it when performing this upgrade.

Change-Id: I2478013b396082ffdc3d99ed86a821ec86ac4c5d
(cherry picked from commit 2d1390f5d2f0ca653d03f936c601cd4cb7a488fd)

Metadata Update from @jmagne:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.5 (was: 10.5)

7 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.5-1.fc27

7 years ago

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/2964

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.

Log in to comment on this ticket.

Metadata