| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
The ansible-core 2.11 release has reached EOL with the release of ansible-core 2.14.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Log `runme.sh` execution in integration tests (#79263)
* Log `runme.sh` execution in integration tests
This patch adds `set -x` where it's missing in the integration tests.
It also enables `pipefail` in `runme.sh` scripts that use pipes.
* Add a change note for PR #79263
(cherry picked from commit 6674c43edd203d1241507c4d857f555a7c844c18)
* Delete a bad PR #79263 change note
(cherry picked from commit 9cfb3f73e8d7f910e226de3aebe6f9b9b18327ec)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Restrict `wheel` below v0.38.0 under Pythons < 3.7
* Add a change note for PR #79187
* Update changelogs/fragments/79187--wheel-0.38.0.yml
Co-authored-by: Matt Clay <matt@mystile.com>
* Use constraints file when installing wheel.
Co-authored-by: Matt Clay <matt@mystile.com>.
(cherry picked from commit a76bbb18a5a80cda0d9683677aa8d5cd8a2e6093)
Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>
|
| |
|
|
|
|
|
| |
(#78852)
(cherry picked from commit 2542048)
Co-authored-by: Matt Martz <matt@sivel.net>
|
| |
|
|
|
|
|
| |
(#78669) (#78671)
(cherry picked from commit 046c59d)
Co-authored-by: Matt Martz <matt@sivel.net>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This specific integration test gets stuck periodically causing the
Galaxy jobs to be killed on timeout wasting an hour of runtime. The
module that gets stuck waiting on Pulp is an in-test one, called
`setup_collections`. When it works, the task is complete in around 70
seconds but when it doesn't, it just freezes the whole play.
This patch attempts to make it fail faster by putting a reasonable
timeout value of 2 minutes.
(cherry picked from commit f1c56e988dbbb769b34a3c80baa40c916b4d0c88)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes pytest errors out with an `ImportError` during its tests
collection stage when a Python package/directory containing the test
module does not have an `__init__.py` in it. This is being observed
under Python 3.9 and higher.
The patch provides a workaround for this problem but does not address
the root cause which is currently unknown.
Ref:
https://github.com/ansible/ansible/pull/78585#issuecomment-1220885431
(cherry picked from commit beb70daf14bc14acad076b34dca39a3ca6b633bb)
|
| |
|
|
|
| |
The paramiko install fails due to the new bcrypt 4.0.0 release.
The test is being skipped on the affected platforms since ansible-core 2.11 will reach end-of-life in November.
|
| |
|
|
|
|
|
| |
On BusyBox systems such as Alpine, chattr on a tmpfs fails with a status of 0 and output only on stderr.
This change updates the test to not assume output on stdout.
(cherry picked from commit 2e536c0afb9008884a0f12e8e650541e0ead76c9)
|
| |
|
|
|
|
|
|
|
| |
* Fix version switcher for Japanese docs (#78432)
(cherry picked from commit 660aceaa777b8847648908e8c978a0518f44cef4)
* update version to match branch
* fix merge change
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add a note on installing faketime on Alpine in CI
(cherry picked from commit d7e3c765be89ae3d155c00198c12dedf14d65816)
* Add note about libuser being unavailable @ Alpine
* Prepare Alpine signing keys for installs from edge
Before this patch, the Ansible Core CI Alpine image integrated into
this branch only had old package signing keys pre-installed.
On July 14, 2022, Apline has rotated their RSA keys to the new
4096-bit ones[1]. This resulted in older unprepared systems being
unable to verify package downloads, causing the following in the logs:
ERROR: http://dl-cdn.alpinelinux.org/alpine/edge/community:
UNTRUSTED signature
This patch updates the system-trusted keys by upgrading the
`alpine-keys` package to the latest version. With the change, the old
package installs succeed again. In particular, this concerns the
`faketime` and `libuser` packages that are used in `group` and
`setup_cron` integration tests.
This change is only applied to ansible-core 2.11 since all the newer
release streams have an updated version of the Alpine container that
does not need this hack.
[1]: https://www.alpinelinux.org/posts/Alpine-edge-signing-keys-rotated.html
|
| |
|
|
| |
(cherry picked from commit 1321d6ecd5d34c9a90d526e4852bfc469bfae4a9)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(#75452)
Rather than adding further complexity to the regex, preprocess the output to
remove any empty lines. Now the only purpose of the regex is to fix
wrapped lines.
Fixes #70949
(cherry picked from commit 51f2f1ac5ee1416f097587ff81b721b3ccc36971)
Co-authored-by: Martin Krizek <martin.krizek@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
(cherry picked from commit f5642cea28299857fd11aa77307f7ee04ef1edb3)
|
| |
|
| |
(cherry picked from commit a3cc6a581ef191faf1c9ec102d1c116c4c2a8778)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes a bug which under certain conditions results in data
returned from lookups not being marked as unsafe.
Each time Templar.do_template is invoked a new AnsibleContext is
created and stored effectively at two places:
1) as an instance variable in templar_obj.cur_context
2) as a local variable called new_context in do_template method of Templar
Due to custom functionality in Ansible's Context that allows for nested
templating it is possible that during resolving variable's value
template/do_template method is called recursively again, again creating
a new context. At that point the problem manifests itself because as
mentioned in 1) above the context is overwriten on the templar object
which means that any subsequent calls to _lookup will use the new
context to mark it as unsafe which is now different to the local
new_context which is used for testing for unsafe property.
The solution to the problem appears to be to restore the original
context inside do_template and also to eliminate the local variable
new_context to prevent problems in the future.
It appears that we don't have a better way of storing the context other
than as some form of global variable and so this appears to be the
"best" solution possible at this point. Hopefully data tagging will be
the solution here.
For more examples see unit and integration tests included in this patch.
Fixes #77535
(cherry picked from commit 3980eb8c09d170a861351f8aff4a1aa1a8cbb626)
|
| |
|
|
| |
Bootstrapping fails due to missing packages.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
(cherry picked from commit fbc75020508605d713355835e7cbbeda576379e4)
|
| |
|
|
|
| |
(#77347)
(cherry picked from commit ff184b0815cdbf7dc222fd9d7b0cfaa93d5fe03c)
|
| |
|
|
|
|
|
|
|
| |
* winrm - ensure callers PATH for kinit is set
* Fix unit test expectations
* Fix type annotation
(cherry picked from commit 60b4200bc6fee69384da990bb7884f58577fc724)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* use same timeout for galaxy api interactions (#77088)
Also, bump the default. A number of people have reported problems with
this 20 second timeout for a couple of years on
https://github.com/ansible/galaxy/issues/2302
It is mentioned in the issue that resolving dns can sometimes take up to
30 seconds, and that this timeout includes dns resolution.
Includes a changelog message
* fix type hint
Co-authored-by: Matt Clay <matt@mystile.com>
Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
Co-authored-by: Matt Clay <matt@mystile.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix collection redirects for filter and test plugins (#77210)
* Fix collection redirects for jinja2 filters/tests
* Handle recursive redirects
Co-authored-by: Matt Martz <matt@sivel.net>
(cherry picked from commit 8063643b4cec51a72377da5f3fa354d3ff9e737a)
* The error message is only capitalized on 2.13. Make test more flexible.
(cherry picked from commit 734777ef05b8c200f45336a8b9b41f9f9af597c1)
|
| |
|
|
|
|
|
|
|
|
|
| |
modified content (#77129)
* Fix 'ansible-galaxy collection verify' to report files/directories not listed in the FILES.json
(cherry picked from commit a1d467dbb21e00cdb0ed38baf0e43e583185dc59)
* changelog
(cherry picked from commit 3d49d6f69ec1afa2234a21a1f9cd273d55cb6597)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#77126)
* [stable-2.11] Use full python package for ansiballz cache filenames (#77090)
* Use full python package for ansiballz cache filenames
* Be a little more explicit about test goals
(cherry picked from commit 8cbe143)
Co-authored-by: Matt Martz <matt@sivel.net>
* linting
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This works around issues on RHEL 7.9 when an old version of pexpect is installed from an OS package.
(cherry picked from commit 27fe26edbf57a39a11de7dea14dc60d4a6b1384e)
Co-authored-by: Matt Clay <matt@mystile.com>
|
| | |
|
| | |
|
| |
|
| |
Signed-off-by: Christian M. Adams <chadams@redhat.com>
|
| |
|
|
|
|
|
| |
The `--boxed` option is deprecated..
(cherry picked from commit eaeec8a65c4bf9066c5a2c180ec11872f84e6b67)
Co-authored-by: Matt Clay <matt@mystile.com>
|
| | |
|
| |
|
|
|
|
|
|
| |
Installation of MarkupSafe 2.1.0 and later require setuptools 39.2 or later,
or a recent version of pip which supports installation using a wheel.
Some systems will not have new enough versions of pip and/or setuptools,
especially virtual environments -- including those created by ansible-test.
|
| |
|
|
|
|
|
|
| |
dependencies (#77091)
(cherry picked from commit 88bfb7193e729578a570e3c73becfc6613f512da)
Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com>
|
| |
|
|
|
|
| |
(cherry picked from commit c27fd777f4d82fc1eefaa20114cf1f76b7ce1bee)
Co-authored-by: Matt Clay <matt@mystile.com>
|
