TKS failover during TPS operations fails
Steps to Reproduce:
1. Create a clone TKS for failover 2. Add new TKS subsystem connection (tks2) using the TPS Web UI and enable it 3. Edit userKey profile to use tks2 (changes were made through Web UI) 4. Create a new sharedSecret key on master TKS and import it to TPS and clone TKS. Edit TPS and clone TKS config to use the new sharedSecret key. 5. Add the following parameters to clone TKS (because they existed in the master TKS with which TPS was configured) tps.0.host=qe-blade-08.idmqe.lab.eng.bos.redhat.com tps.0.nickname=sharedSecret tps.0.port=25443 tps.0.userid=TPS-qe-blade-08.idmqe.lab.eng.bos.redhat.com-25443 6. Shut down master TKS and attempt token enrollment
Actual results:
Token enrollment fails
Expected results:
Token enrollment operation should failover to clone TKS and should be successful
Additional info:
debug log attached to associated Bugzilla Bug
Per PKI Bug Council of 10/18/2016: 10.3
cfu to investigate
Roshni 2016-10-25 13:31:19 EDT
I was not able to reproduce the issue in comment 12 using fresh instances. Enroll/format operations are successful as expected during failover.
Metadata Update from @rpattath: - Issue set to the milestone: 10.3.6
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: worksforme (was: Invalid)
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/2641
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.