Service atomic-openshift-master-api.service did not restart sometime properly after reboot

Issue

• We have a Openshift 3.1 native Master-Master environment. If I reboot a master, the atomic-openshift-master-api service will sometimes not start.

journalctl -flu atomic-openshift-master-api

-- Logs begin at Wed 2015-12-30 12:52:20 CET. --
Dec 30 12:52:41 ose-master2.openshift.com atomic-openshift-master-api[1182]: I1230 12:52:41.055843    1182 plugins.go:71] No cloud provider specified.
Dec 30 12:52:41 ose-master2.openshift.com atomic-openshift-master-api[1182]: I1230 12:52:41.356007    1182 start_master.go:388] Starting master on 0.0.0.0:8443 (v3.1.0.4-16-g112fcc4)
Dec 30 12:52:41 ose-master2.openshift.com atomic-openshift-master-api[1182]: I1230 12:52:41.356074    1182 start_master.go:389] Public master address is https://ose-master.openshift.com:8443
Dec 30 12:52:41 ose-master2.openshift.com atomic-openshift-master-api[1182]: I1230 12:52:41.356116    1182 start_master.go:393] Using images from "openshift3/ose-<component>:v3.1.0.4"
Dec 30 12:52:41 ose-master2.openshift.com atomic-openshift-master-api[1182]: I1230 12:52:41.423554    1182 run_components.go:183] Using default project node label selector:
Dec 30 12:52:42 ose-master2.openshift.com atomic-openshift-master-api[1182]: F1230 12:52:42.431378    1182 controller.go:83] Unable to perform initial IP allocation check: unable to persist the updated service IP allocations: serviceipallocation "" cannot be updated: the provided resource version does not match
Dec 30 12:52:42 ose-master2.openshift.com systemd[1]: atomic-openshift-master-api.service: main process exited, code=exited, status=255/n/a
Dec 30 12:52:42 ose-master2.openshift.com systemd[1]: Failed to start Atomic OpenShift Master API.
Dec 30 12:52:42 ose-master2.openshift.com systemd[1]: Unit atomic-openshift-master-api.service entered failed state.
Dec 30 12:52:42 ose-master2.openshift.com systemd[1]: atomic-openshift-master-api.service failed..