#2646 Dogtag sometimes fail to respond to status request
Closed: duplicate 6 years ago Opened 6 years ago by stlaz.

It would seem that Dogtag would fail to respond reply to a status request. The detailed description of this problem can be found at:
https://pagure.io/freeipa/issue/6766


Unfortunately, a bug in "Pagure" does not allow one to specify the PKI "default" Milestone "0.0 NEEDS_TRIAGE"; as a consequence bugs coming in without Milestones may not be "discovered" initially.

Filed https://pagure.io/pagure/issue/2246 - [RFE] - Ability to programmatically specify "default" Milestone

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: ---

6 years ago

Per PKI Bug Council of 04/27/2017: Leave in NEEDS_TRIAGE

May be fixed by fix to "https://pagure.io/dogtagpki/issue/2644 - pkispawn returns before tomcat is ready" in which case this will be closed as a duplicate.

Per PKI Bug Council of 07/06/2017: Closing as duplicate of "https://pagure.io/dogtagpki/issue/2644 - pkispawn returns before tomcat is ready".

Please re-open this issue if it still persists.

Metadata Update from @mharmsen:
- Issue close_status updated to: duplicate
- Issue set to the milestone: 10.4.4 (was: 0.0 NEEDS_TRIAGE)
- Issue status updated to: Closed (was: Open)

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

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