Run script generate-gitmodules.py to sync with governace repository to
add new repositories and remove retired ones.
Change-Id: Ia42b717ad242958ba4a9689ac814c956f460712f
* Update ansible-role-puppet from branch 'master'
- Add flag to control logging the rsyncs
rsyncing the puppet modules can be super chatty and not super
interesting. Add a flag to turn it off.
Change-Id: I7206955aeb335adafb8625c89d8b8a70078d666c
* Update ansible-role-puppet from branch 'master'
- Add color parameter
When we're logging inside of ansible, turning off ansi colors can
be nice. Especially inside of Zuul.
Change-Id: I719ebb106fbb31795cc02c9504507bdae607bcdd
* Update ansible-role-puppet from branch 'master'
- Merge "Revert "Don't log puppot module sync""
- Revert "Don't log puppot module sync"
This reverts commit 7b47277e3e7fba995b88079dfbb7e9c6af2a5081.
It turns out that for some reason this boring operation does actually go
wrong[1], and if logging doesn't happen then we don't know why.
[1] http://logs.openstack.org/00/616000/6/check/infra-puppet-apply-4-ubuntu-xenial/7379d8c/applytest/puppetapplytest44.final.out.FAILED
Change-Id: I2ce9c3d79385fc0a01b3a5fc85fa4bf4128c25bc
* Update ansible-role-puppet from branch 'master'
- Clear out old facts
In debugging why I631e3e3592a9be5c7da642cf34eec6d9758bf161 was not
rolling out to the zuul executors, I eventually found
/etc/facter/facts.d/ansible.json was present on a number of hosts and
effectively pinning the project-config checkout to an old reference.
Given the dates around file creation and the pinned change number, it
seems very likely something happened during the openstack->opendev
transition where some hosts had ansible run with a specific
project_config_ref set as a fact. Although the fact is now unset,
nothing will ever clear the old ansible.json which keeps applying.
We could remove all stale files by hand; but a) it's not clear where
it ran (although likely only hosts starting with z*) and b) we leave a
chance for it to happen again.
We could clear this after every puppet run; but it seems like this
role should leave the system largely in the state it ran puppet in.
Thus this clears out the file before the puppet run if no facts are
given. This should fix our immediate issue on all hosts.
Change-Id: I96adf4fb77f06b18fe73b6f10d1b07b7fe44385f
* Update ansible-role-puppet from branch 'master'
- Fix ansible-lint
The current tests never fail, change ansible-lint invocation so that it
fails - and fix problems.
Change-Id: I6aeb1e3a4c28af71a858ec83c21f4dbb5e7ef97f
* Update ansible-role-puppet from branch 'master'
- Switch to linters job
Prepare deprecation of ansible-lint job and use linters job instead.
Create a new tox environment for this.
Add job to run linters job.
Needed-By: https://review.opendev.org/658682
Change-Id: Ib2c7bdc66077442993d017cf97a4a8116799d130
- 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.
* Update ansible-role-puppet from branch 'master'
- Fix hieradata path for puppet 4
The datadir symlink points to /opt/system-config, but the private
hieradata actually lies within /opt/system-config/hieradata.
Change-Id: Iefedf1d733701c7abebd5022ca98993c5fcbd8a3