dogtagpki

#250 Creating/removing custom instances should not require http/ajp ports
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

Creating a subsystem that uses a non-default instance name via command line parameters requires specifying the http, https, and ajp ports:

# pkispawn -v -f ca.cfg -s CA -i master -d pki
ERROR:  When a custom 'CA' subsystem is being deployed, the 'instance', 'http_port', 'https_port', and 'ajp_port' must ALL be specified!
# pkispawn -v -f ca.cfg -s CA -i master -d pki --http_port 8080 --https_port 8443 --ajp_port 8009
(works)

If the instance name is specified in the config file:

pki_instance_name=pki-master

the following command will work just fine:

# pkispawn -v -f ca.cfg -s CA

However, removing this instance also requires specifying the ports:

# pkidestroy -s CA
ERROR:  File '/etc/sysconfig/pki/tomcat/tomcat/ca/pkideployment.cfg' is either missing or is NOT a regular file!
# pkidestroy -s CA -i master -d pki --http_port 8080 --https_port 8443 --ajp_port 8009
(works)

Changes were made to the following files to address this issue:

* pki/base/deploy/src/scriptlets/pkiconfig.py
* pki/base/deploy/src/scriptlets/pkiparser.py

RESOLVED:

commit 14243746edd14be2564b625c4a940c4723c168f1
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Tue Jul 24 11:28:29 2012 -0700

PKI Deployment Scriptlets
- PKI TRAC Ticket #244 - Non-user-friendly message when deleting non-existen
  subsystem with pkidestroy
- PKI TRAC Ticket #246 - Incorrect parameter names in pkispawn configuration
- PKI TRAC Ticket #248 - pki_ds_database should not be a DN
- PKI TRAC Ticket #249 - pki_ds_base_dn causing pkispawn failure
- PKI TRAC Ticket #250 - Creating/removing custom instances should not requi
  http/ajp ports
- PKI TRAC Ticket #251 - Instance name may conflict with other files
- PKI TRAC Ticket #253 - Fix pki-destroy removal of
  '/var/log/pki/{pki_instance_id}' directory . . .
- PKI TRAC Ticket #254 - Dogtag 10: Fix spec file to build successfully via 
  on Fedora 17 . . .
- PKI TRAC Ticket #255 - Missing resteasy-atom-provider.jar
- PKI TRAC Ticket #260 - Dogtag 10: Change the layout of 'pki_instance_id' . . .

Metadata Update from @edewata:
- Issue assigned to mharmsen
- Issue set to the milestone: Dogtag 10.0 Alpha

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

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.
Metadata
None
None
None
Normal
defect
Installation/Configuration
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.