dogtagpki

#1453 pkispawn of Clone CA is successful when pki_clone_replication_master_port has a wrong port number
Closed: migrated by dmoluguw. Opened by rpattath.

Closed: migrated
Reopen Issue

pkispawn of Clone CA is successful when pki_clone_replication_master_port has a
wrong port number (not the one actually being used by MASTER CA)

Steps to Reproduce:

1. pkispawn clone CA with config file having wrong port number for the param
pki_clone_replication_master_port

Actual results:

pkispawn is successful

Expected results:

pkispawn should give an error that pki_clone_replication_master_port is not
reachable

The following is from 'https://fedorahosted.org/pki/ticket/1452 PKI TRAC Ticket #1452 - Descriptive error message should be shown when pki_clone_replication_clone_port is invalid' which has been marked as a duplicate of this ticket:

Descriptive error message should be shown when pki_clone_replication_clone_port is invalid instead of throwing a java exception with Internal Server error

Steps to Reproduce:

  1. Clone a CA where the inf has an invalid (non-existing) value for
    pki_clone_replication_clone_port

Actual results:

pkispawn : ERROR ....... Exception from Java Configuration Servlet: 500
Server Error: Internal Server Error
pkispawn : ERROR ....... ParseError: not well-formed (invalid token):
line 1, column 0: {"Attributes":{"Attribute":[]},"ClassName":"com.netscape.cert
srv.base.PKIException","Code":500,"Message":"Error in populating database:
java.io.IOException: Failed to setup the replication for cloning."}

Expected results:

Descriptive error message stating the port is invalid or not reachable

Per CS/DS Meeting of 07/06/2015: 10.3

Per IRC discussion with alee, I confirmed that this is 10.4.

Metadata Update from @rpattath:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field lowhangingfruit adjusted to vakwetu: X
- 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: UNTRIAGED)

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1237280)

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Normal
defect
Installation/Configuration
QE
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.