Description of problem: === atomic-openshift-master-api service stop working after restarting systemd-journald.service Version-Release number of selected component (if applicable): === OCP 3.2 How reproducible: === Steps to Reproduce: 1. Restart systemd-journald (# systemctl restart systemd-journald.service) 2. Wait for 3 or 5 minutes 3. Check status of api service Actual results: === # systemctl is-active atomic-openshift-master-api.service inactive # curl -k https://localhost:8443/ curl: (7) Failed connect to localhost:8443; Connection refused Expected results: === atomic-openshift-master-api.service should not be effected restart of systemd-journald service Additional info: === After atomic-openshift-master-api was down, it will not be fixed by restarting the atomic-openshift-master-api service. It needs system reboot.
This is the same fundamental issue as found here: https://bugzilla.redhat.com/show_bug.cgi?id=1378929 We are exploring systemd host level configuration options that would prevent this problem from occurring.
Moving this to the installer as it should be fixed in concert with https://bugzilla.redhat.com/show_bug.cgi?id=1378929
*** This bug has been marked as a duplicate of bug 1378929 ***