* Update ansible-role-chrony from branch 'master'
to 565e1d0c46df3a80dee460a37c9cf8261370b469
- Retire Tripleo: remove repo content
TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145
this commit remove the content of this project repo
Change-Id: I1a42c6119429e588a8dbb24fb8687dcc4ed2a3a5
* Update ansible-role-chrony from branch 'master'
to 0111661102ebb211ce8e1a08df57fb51cb4671fb
- Add chrony_config_file_location default to avoid uncontrolled failures
This patch adds a missing config that let any playbook fail if no vars
are passed. Even though it's always good overriding variables, we should
provide defaults for config files like any other first citizen parameter.
Change-Id: I953296e22a6d8310aaf401fd9b13a71c35dbaf6a
* Update ansible-role-chrony from branch 'master'
to 9528e8a0b75dbb8f6f9c0867766f69a8b077d611
- Add tasks for run and sync to chrony role
- Moves some of the tasks from config.yml that are actually used to run
the chronyd into a new dedicated run.yml tasks file.
- Adds a sync.yml with tasks for actually syncing using chronyc.
- Adds some install tasks to install.yml to disable ntpd in case it is
running as it's not compatible when chronyd is also running.
- Refactors the distro variable loading into a common tasks vars.yml
that can be reused by the other tasks files
- Adds a symbolic link 'chrony' to the top level directory of the
project, since the role is named 'chrony', and ansible searches for a
directory with that name.
Signed-off-by: James Slagle <jslagle@redhat.com>
Change-Id: I673ce4fc17dd98aa251fdffce73bf9a096aad6fb
* Update ansible-role-chrony from branch 'master'
to 7ccf873c82f12adda204c05f53adb3ff6be3fc0b
- Change chrony_role_action default to 'all'
As documented we should change the default to 'all'.
Also fixes tox-linters job.
Change-Id: I33bf616bcca62f68437a0c2520cb860194a3a203
* Update ansible-role-chrony from branch 'master'
to 1b82e87cdf0b0da67770a0abd64ea0e3570f5f43
- Replacing chrony-helper with chronyc
There's no helper in centos9.
Change-Id: Iae81ee00baa323fbff3df93029253337b635ec7e
* Update ansible-role-chrony from branch 'master'
to 14b34c20e5825fca216ae810aa8e50910c90578d
- Create chrony-online service
NetworkManager has a dispatcher which may cause the sources to be marked
as disabled. If you don't have any interfaces actually managed with
NetworkManager, we need to have a way to ensure that the sources get
marked enabled on boot. This change adds a chrony-online service that
waits for the network-online.target in order to be able to make chronyd
source online.
Change-Id: Ib1d91852d281c63b2458fc3c0199a5d5fed17056
* Update ansible-role-chrony from branch 'master'
to ae5374e14ab56cd68629bb52e55650b606c5d0b0
- Switch to centos8 standalone job
This repo still had the centos 7 standalone jobs defined. Let's upgrade
it to centos 8 for now.
Change-Id: I23f95be02a5a3fd025574a4aa68f0b89ed4ff57e
* Update ansible-role-chrony from branch 'master'
to 15ad50777e976055eb5a1b85a9841ae268714f78
- Correct the tox option for skipping sdist generation
The tox option to skip source distribution building is skipsdist,
but this seems to be often misspelled skipdist instead, which gets
silently ignored and so does not take effect. Correct it
everywhere, in hopes that new projects will finally stop copying
this mistake around.
See https://tox.readthedocs.io/en/latest/config.html#conf-skipsdist
and https://github.com/tox-dev/tox/issues/1388 for details.
Change-Id: I930b16a0834d893080386b40989fa517f1bc343b
* Update ansible-role-chrony from branch 'master'
to 5580549164358b6d18f922d82a44e3ec948868bf
- setup.cfg: Replace dashes with underscores
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I7112c11085d646e17fa2beb792a0aeed0d56e66b
* Update ansible-role-chrony from branch 'master'
to 28193e49e69cf8deff5c19f43833d34afd694b31
- Use ansible_facts
ansible_distribution and ansible_os_family rely on the facts being
injected as vars. This change switches our vars file lookup to use
ansible_facts instead.
Change-Id: Ia6636bf0223f7e51b6b50950a5c8c1413b4a54b0
* Update ansible-role-chrony from branch 'master'
to 24f495b820d617581475a8082f34168d3987986f
- Fix requirements
Cap ansible at <2.10 and fix hacking
Change-Id: I509b642e2c1ddb95c7d4a94a134f0c4e1b8ff8e2
* Update ansible-role-chrony from branch 'master'
- Replace deprecated UPPER_CONSTRAINTS_FILE variable
UPPER_CONSTRAINTS_FILE is deprecated and TOX_CONSTRAINTS_FILE is
the new environment variable name that replaces it [1].
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
[2] https://review.opendev.org/#/c/722814/
Change-Id: I5c93f7e942b1b73023e4e26cdf4a3e5ea957c925
* Update ansible-role-chrony from branch 'master'
- Bump pyflakes
We need a python 3.9 compatible version.
Related PyCQA/pyflakes #367
Change-Id: Ief43d5fbad16f86737680841a35f3137e259a7f3
* Update ansible-role-chrony from branch 'master'
- Merge "Fix the misspelling of "configuration""
- Fix the misspelling of "configuration"
Change-Id: I7b9d0557a6abec1ae4de2ab9cc679238284b21d0
* Update ansible-role-chrony from branch 'master'
- Avoid hard-coded value in a generic ansible role
The service will be enabled if and only if its state is set to "running"
or "started".
This change addresses comment in this change:
https://review.opendev.org/#/c/669365/1/tasks/config.yml@14
Change-Id: Ic25772c04047bcd3aaa3e8abc5b947feb66bcbbb
* Update ansible-role-chrony from branch 'master'
- Ensure service is enabled
With older tripleo versions, we did disable the service since we were
using ntpd.
If we upgrade from a version using ntpd, the chronyd service won't be
active upon reboot.
Change-Id: Ic59374afdf5ace02ba8243f5163d0950e527ec52
Closes-Bug: #1835368
* Update ansible-role-chrony from branch 'master'
- Merge "Change openstack-dev to openstack-discuss"
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
- Change openstack-dev to openstack-discuss
Mailinglists have been updated. Openstack-discuss replaces openstack-dev.
Change-Id: Ic023d60e68522c1511a4b85334704a0b7fd12e7f
* Update ansible-role-chrony from branch 'master'
- Force chrony restart on config change
We've seen handlers being inconsitently being ignored for some
deployments when we force a handler flush mid-playbook. We'll need to
ensure the config is properly loaded if we want to follow up with
subsequent chronyc application so it's best to always invoke the restart
when the configuration actually changes.
Change-Id: I5292f1b1bd65cef340e1e9742463620effc30d26
Ghanshyam Mann