ntpd on fuel master not started after reboot

Bug #1688631 reported by Alexandru Avadanii
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Alexandru Avadanii
Nominated for Ocata by Michael Polenchuk
Newton
Won't Fix
High
Unassigned

Bug Description

Steps to reproduce:
- install Fuel Master node (no need to proceed with Openstack installation);
- check ntpd state (`service ntpd status` will report it as running);
- reboot Fuel Master node
- check ntpd state again (this time it won't be running);

Expected results:
- NTPd is started automatically after Fuel Master is installed;
- NTPd is started automatically after Fuel Master node is rebooted;
- Openstack deployment using Fuel Master NTP works (before and/or after master reboot);

Actual result:
- NTPd is started after Fuel Master is installed;
- NTPd is NOT started after Fuel Master is rebooted;
- Openstack deployment using Fuel Master NTP fails if NTPd is not running;

Reproductibility:
- always

Description of the environment:
- OPNFV Pharos lab;

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

Fix proposed to branch: master
Review: https://review.openstack.org/463037

Changed in fuel:
assignee: nobody → Alexandru Avadanii (alexandru-avadanii)
status: New → In Progress
Changed in fuel:
milestone: none → 12.0
importance: Undecided → Medium
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-main (master)

Change abandoned by Alexandru Avadanii (<email address hidden>) on branch: master
Review: https://review.openstack.org/463037
Reason: Sorry, this fix does not really work. I will try to take another look when I find some time ...

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

We are not going to fix this bug.

Changed in fuel:
status: In Progress → Won't Fix
Revision history for this message
Alexandru Avadanii (alexandru-avadanii) wrote :

For the record, the actual issue was a conflict between 'chronyd' and 'ntpd' services, both enabled by default. Disabling 'chronyd' service manually works.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.