Enabling all subsystems on startup

[pki-bot]

This issue was migrated from Pagure Issue #2699. Originally filed by edewata (@edewata) on 2017-05-22 12:22:29:

• Closed at 2017-05-23 15:32:26 as fixed
• Assigned to edewata (@edewata)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1454471

---

Currently if selftest fails during startup the subsystem will undeploy (i.e. disable) itself to prevent partially running service which could confuse other services that depend on it.

The admin is expected to investigate and fix the failure, then reenable the subsystem manually with this command (see http://pki.fedoraproject.org/wiki/SelfTest):

$ pki-server subsystem-enable ca

The selftest error and the instruction to reenable the subsystem is written into the log, but often times the admin does not notice that immediately, leading to confusions.

One possible solution is to automatically reenable all subsystems on Tomcat restart. If the selftest is still failing the subsystem will shut itself down as before, but at least the admin is no longer required to reenable the subsystem manually.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-05-22 16:24:55

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 assigned to edewata
• Issue priority set to: critical
• Issue set to the milestone: 10.4

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-05-22 16:28:05

Metadata Update from @mharmsen:

• Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1454471

[pki-bot]

Comment from edewata (@edewata) at 2017-05-22 20:10:51

Patches:

• https://review.gerrithub.io/#/c/362078/

[pki-bot]

Comment from edewata (@edewata) at 2017-05-23 15:05:56

Fixed in master:

• 8016ed7

[pki-bot]

Comment from edewata (@edewata) at 2017-05-23 15:32:32

Metadata Update from @edewata:

• Issue close_status updated to: fixed
• Issue set to the milestone: 10.4.5 (was: 10.4)
• Issue status updated to: Closed (was: Open)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-05-23 16:48:02

Metadata Update from @mharmsen:

• Issue set to the milestone: 10.4.6 (was: 10.4.5)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-06-07 18:06:15

Metadata Update from @mharmsen:

• Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27