p_ntp resource is not restarted by pacemaker if 'ntpd' started by /etc/init.d/ntpd script
Bug #1432071 reported by
Dennis Dmitriev
This bug report is a duplicate of:
Bug #1431357: System ntpd init script can break crm p_ntp resource.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
New
|
High
|
Oleksiy Molchanov | ||
Bug Description
If 'ntpd' started by system init script on controllers (during reboot or manual restart of service) , pacemaker believes that ntpd is working properly (by checking 'ntpd.pid' file and PID of 'ntpd' process).
But in this case, 'ntpd' is not listening to vip__management IP. That makes the 'ntpd' service unavailable on the controller for all the rest nodes of the cluster.
Pacemaker script 'ns_ntp' in "status" should check that the 'ntpd' process started in the 'vrouter' namespace, and restart the resource otherwise.
http://
| Changed in fuel: | |
| assignee: | Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov) |
To post a comment you must log in.
