#2379 Strange Certificate Error, ipa-server-install ERROR 'b64_cert'
Closed: duplicate 6 years ago Opened 7 years ago by mharmsen.

Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes 30
seconds:

  [1/28]: creating certificate server user
  [2/28]: configuring certificate server instance
  [3/28]: stopping certificate server instance to update CS.cfg
  [4/28]: backing up CS.cfg
  [5/28]: disabling nonces
  [6/28]: set up CRL publishing
  [7/28]: enable PKIX certificate path discovery and validation
  [8/28]: starting certificate server instance
  [9/28]: creating RA agent certificate database
  [10/28]: importing CA chain to RA certificate database
  [11/28]: fixing RA database permissions
  [12/28]: setting up signing cert profile
  [13/28]: setting audit signing renewal to 2 years
  [14/28]: restarting certificate server
  [15/28]: requesting RA certificate from CA
  [16/28]: issuing RA agent certificate
  [error] KeyError: 'b64_cert'
ipa.ipapython.install.cli.install_tool(Server): ERROR    'b64_cert'

Post CSR generation, not sure how to proceed. Very unhappy about this not
being a more module installation, as minor common problems demand a full
uninstall and reinstall.. which then requires a resign every time, dramatically
increasing troubleshooting time.

Additional Information:

Created attachment 1167955 in associated bug:
ipaserver-install.log

Per PKI Bug Council of 06/23/2016: 10.4

Per Offline Triage of 11/30/2016-12/01/2016: 10.4 - major

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4

7 years ago

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: FUTURE (was: 10.4)

6 years ago

Metadata Update from @ftweedal:
- Issue assigned to ftweedal

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: minor (was: major)
- Issue set to the milestone: 10.5 (was: FUTURE)

6 years ago

[20171025] - Offline Triage ==> 10.6

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

6 years ago

Nice pickup @cheimes. Yeah I think this is now resolved as part of #2909, so I'll close
as duplicate.

Metadata Update from @ftweedal:
- Issue close_status updated to: duplicate

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6.0 (was: 10.6)

6 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/2499

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.

Login to comment on this ticket.

Metadata