#3124 pki-server status cannot handle custom name
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by dmoluguw.

pkidaemon status has been replaced by pki-server status. However, pki-server status cannot report status of custom instances.

For instance, pkidaemon status reported status of all available instances. pki-server status can report only status of pki-tomcat instance. There is no option to provide custom instance name.

Acceptance criteria:

pki-server status should report status of all available instances (ie) mimic pkidaemon status

PS: This applies to pki-server [start|stop|restart|remove|create]


The pki-server tool generally works on one instance at a time. The start/stop/restart/remove/create commands take an optional instance ID argument so you should be able to specify a different instance ID. Could you try pki-server status <instance>?

Metadata Update from @edewata:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

4 years ago

Yes, pki-server status <instance ID> works!

Few questions:/observations:

  1. Since pkidaemon status reported ALL instances in a system and since it was replaced by pki-server status, shouldn't the latter mimic the deprecated tool?

  2. (nitpick) The general pattern for providing instance name to pki-server is through -i <instance>. But, this one does not accept -i. Do we want to make it uniform?

My 2c ;-)

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

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)

3 years ago

Login to comment on this ticket.

Metadata