Internal 500 error because of systemd is starting pki too early?

[pki-bot]

This issue was migrated from Pagure Issue #3015. Originally filed by mharmsen (@mharmsen) on 2018-05-02 20:21:44:

• Assigned to jmagne (@jmagne)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1555422

---

Possible issue with order of services startup?

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-02 20:22:32

Per 10.5.x/10.6 Triage: 10.5

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-02 20:22:33

Metadata Update from @mharmsen:

• 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1555422
• Custom field type adjusted to None
• Custom field version adjusted to None

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-04 14:42:16

Metadata Update from @mharmsen:

• Issue assigned to jmagne

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-04 14:45:19

Metadata Update from @mharmsen:

• Issue priority set to: critical (was: major)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-04 19:24:19

Metadata Update from @mharmsen:

• Issue priority set to: blocker (was: critical)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-04 19:24:56

Moved to "blocker" status to raise priority for next release