Actions
Bug #15139
closedStart foreman-proxy after extensions are finished
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Image
Description
If extensions drops external facts, foreman-proxy must start afterwards otherwise new facts won't be loaded properly.
Updated by Lukas Zapletal almost 9 years ago
- Status changed from New to Rejected
Looks like proxy is already starting before extensions fires up:
root/etc/systemd/system/discovery-start-extensions.service
3:Before=discovery-register.service foreman-proxy.service
Thus I am closing this one.
Actions