[Openstack-security] [Bug 1604042] Re: service name should be chronyd not chrony in V-38620 - Synchronize system clock (enable chrony)

Major Hayden major at mhtx.net
Tue Jul 19 14:39:24 UTC 2016


Sorry, the last part of that paste should have been:

[root at centos-osas-test openstack-ansible-security]# systemctl status chrony
● chrony.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

-- 
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1604042

Title:
  service name should be chronyd not chrony in V-38620 - Synchronize
  system clock (enable chrony)

Status in openstack-ansible:
  In Progress

Bug description:
  service name should be chronyd not chrony for V-38620 (Centos 7)

  openstack/openstack-ansible-security:

  diff --git a/tasks/misc.yml b/tasks/misc.yml
  index 733aa4b..c26af06 100644
  --- a/tasks/misc.yml
  +++ b/tasks/misc.yml
  @@ -109,7 +109,7 @@

   - name: V-38620 - Synchronize system clock (enable chrony)
     service:
  -    name: chrony
  +    name: chronyd
       state: started
       enabled: yes
     when: not check_mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1604042/+subscriptions




More information about the Openstack-security mailing list