We've seen cases where pkispawn has failed because the hostname of the machine is set to something like localdomain (instead of , for example, localhost.localdomain).
The most recent example of this is in devstack, where we are trying to set up a KRA/CA to test barbican code as a dev gate.
Its not clear that we actually need this domain name -- (ssl server cert issue?)
I propose that we consider either changing this test or adding an option to allow installers to bypass it.
Pretty sure this is already fixed.
Metadata Update from @vakwetu: - Issue set to the milestone: 10.4
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: None (was: Fixed) - Issue set to the milestone: 10.4.0 (was: 10.4)
Metadata Update from @mharmsen: - Issue close_status updated to: fixed
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/2049
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.