Galaxy collection install dependency fails mysteriously #80048
Labels
Comments
|
Files identified in the description: If these files are incorrect, please update the |
ansibot
added
affects_2.14
bug
|
You would need to specify |
|
By default, pre-releases are excluded, unless requested directly via a specific version or a CLI flag IIRC. So if your collection does not have "stable" releases, and only has alphas/betas/etc, this is the expected behavior. Other package managers, like pip, work similarly. |
|
Though, I suppose that it's reasonable to turn this into a feature request. We could extend the output to mention that pre-releases are not requested. |
|
Ah, understood! However, I think the interface should reflect this? Looking at it now, it strongly indicates that
Should I open a separate issue for this? Would issues pertaining to the Galaxy website UI be appropriate here? |
Either that, or if there are only pre-releases and no stable yet available, the suggested installation command includes I am not sure I have seen alphas and betas in other Galaxy collections. I assume once there is a stable release, newer pre-releases are no longer automatically selected under Just to be clear, should I close this and reference it in a new feature request or is it easier to keep it all in one place? |
|
The Galaxy package index is a separate project (kinda). The CLI (this project) only interacts with its API. So the web-service is able to make its own decisions, accessing its database directly. If we were to implement this on the client side, we'd be hitting the API rate limits even more often. Let's keep the issue open. We have weekly team calls to go through the issues that have the triage needed label. We'll decide on one of those. |
|
Sounds good! Thanks for your attention to detail on this! |
mkrizek
removed
the
needs_triage
Trying to determine if the root cause of the dependency resolution error is due to a pre-release would add a lot of complexity. Although it may not always be applicable, just including the hint in the error message seems like the easiest solution here. I've opened #81147 to fix this. |
webknjaz
added a commit
to webknjaz/ansible
that referenced
this issue
Sep 14, 2023
This patch is aimed at allowing the dependency resolver to actually consider pre-release versions of collections that don't have any stable releases published without `--pre` being requested explicitly. Fixes ansible#80048
I was wrong, the dependency resolver already queries the entire list of versions for each collection so the data is already there. I attempted to solve this in #81606. |
webknjaz
added a commit
that referenced
this issue
Sep 20, 2023
…g collection dependency tree PR #81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref #73416 Ref #79112 Fixes #79168 Fixes #80048 Resolves #81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com>
webknjaz
added a commit
to webknjaz/ansible
that referenced
this issue
Sep 21, 2023
…g collection dependency tree PR ansible#81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref ansible#73416 Ref ansible#79112 Fixes ansible#79168 Fixes ansible#80048 Resolves ansible#81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05)
webknjaz
added a commit
to webknjaz/ansible
that referenced
this issue
Sep 21, 2023
…g collection dependency tree PR ansible#81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref ansible#73416 Ref ansible#79112 Fixes ansible#79168 Fixes ansible#80048 Resolves ansible#81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05)
webknjaz
added a commit
to webknjaz/ansible
that referenced
this issue
Sep 21, 2023
…g collection dependency tree PR ansible#81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref ansible#73416 Ref ansible#79112 Fixes ansible#79168 Fixes ansible#80048 Resolves ansible#81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05)
webknjaz
added a commit
to webknjaz/ansible
that referenced
this issue
Sep 21, 2023
…g collection dependency tree PR ansible#81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref ansible#73416 Ref ansible#79112 Fixes ansible#79168 Fixes ansible#80048 Resolves ansible#81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05)
This was referenced Sep 21, 2023
sivel
pushed a commit
that referenced
this issue
Sep 26, 2023
…g collection dependency tree (#81746) PR #81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref #73416 Ref #79112 Fixes #79168 Fixes #80048 Resolves #81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05)
sivel
pushed a commit
that referenced
this issue
Oct 3, 2023
…pendencies when resolving collection dependency tree (#81747) * Always allow "no-other-choice" pre-release dependencies when resolving collection dependency tree PR #81606. Prior to this patch, when `--pre` CLI flag was not passed, the dependency resolver would treat concrete collection dependency candidates (Git repositories, subdirs, tarball URLs, or local dirs or files etc) as not meeting the requirements. This patch makes it so pre-releases in any concrete artifact references, and the ones being specifically pinned dependencies or user requests, met anywhere in the dependency tree, are allowed unconditionally. This is achieved by moving the pre-release check from `is_satisfied_by()` to the `find_matches()` hook, following the Pip's example. As a bonus, this change also fixes the situation when a collection pre-releases weren't considered if it didn't have any stable releases. This now works even if `--pre` wasn't requested explicitly. Finally, this patch partially reverts commit 6f4b4c3, except for the tests. And it also improves the `--pre` hint warning to explain that it mostly affects Galaxy/Automation Hub-hosted collection releases. Ref #73416 Ref #79112 Fixes #79168 Fixes #80048 Resolves #81605 Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com> (cherry picked from commit 7662a05) * Shorten the collection namespace and name @ tests This is needed on the 2.15 branch which uses older galaxy containers that have restricted FQCN size.
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Nov 17, 2023
v2.16.0 ======= Minor Changes ------------- - Add Python type hints to the Display class (ansible/ansible#80841) - Add ``GALAXY_COLLECTIONS_PATH_WARNING`` option to disable the warning given by ``ansible-galaxy collection install`` when installing a collection to a path that isn't in the configured collection paths. - Add ``python3.12`` to the default ``INTERPRETER_PYTHON_FALLBACK`` list. - Add ``utcfromtimestamp`` and ``utcnow`` to ``ansible.module_utils.compat.datetime`` to return fixed offset datetime objects. - Add a general ``GALAXY_SERVER_TIMEOUT`` config option for distribution servers (ansible/ansible#79833). - Added Python type annotation to connection plugins - CLI argument parsing - Automatically prepend to the help of CLI arguments that support being specified multiple times. (ansible/ansible#22396) - DEFAULT_TRANSPORT now defaults to 'ssh', the old 'smart' option is being deprecated as versions of OpenSSH without control persist are basically not present anymore. - Documentation for set filters ``intersect``, ``difference``, ``symmetric_difference`` and ``union`` now states that the returned list items are in arbitrary order. - Record ``removal_date`` in runtime metadata as a string instead of a date. - Remove the ``CleansingNodeVisitor`` class and its usage due to the templating changes that made it superfluous. Also simplify the ``Conditional`` class. - Removed ``exclude`` and ``recursive-exclude`` commands for generated files from the ``MANIFEST.in`` file. These excludes were unnecessary since releases are expected to be built with a clean worktree. - Removed ``exclude`` commands for sanity test files from the ``MANIFEST.in`` file. These tests were previously excluded because they did not pass when run from an sdist. However, sanity tests are not expected to pass from an sdist, so excluding some (but not all) of the failing tests makes little sense. - Removed redundant ``include`` commands from the ``MANIFEST.in`` file. These includes either duplicated default behavior or another command. - The ``ansible-core`` sdist no longer contains pre-generated man pages. Instead, a ``packaging/cli-doc/build.py`` script is included in the sdist. This script can generate man pages and standalone RST documentation for ``ansible-core`` CLI programs. - The ``docs`` and ``examples`` directories are no longer included in the ``ansible-core`` sdist. These directories have been moved to the https://github.com/ansible/ansible-documentation repository. - The minimum required ``setuptools`` version is now 66.1.0, as it is the oldest version to support Python 3.12. - Update ``ansible_service_mgr`` fact to include init system for SMGL OS family - Use ``ansible.module_utils.common.text.converters`` instead of ``ansible.module_utils._text``. - Use ``importlib.resources.abc.TraversableResources`` instead of deprecated ``importlib.abc.TraversableResources`` where available (https:/github.com/ansible/ansible/pull/81082). - Use ``include`` where ``recursive-include`` is unnecessary in the ``MANIFEST.in`` file. - Use ``package_data`` instead of ``include_package_data`` for ``setup.cfg`` to avoid ``setuptools`` warnings. - Utilize gpg check provided internally by the ``transaction.run`` method as oppose to calling it manually. - ``Templar`` - do not add the ``dict`` constructor to ``globals`` as all required Jinja2 versions already do so - ansible-doc - allow to filter listing of collections and metadata dump by more than one collection (ansible/ansible#81450). - ansible-galaxy - Add a plural option to improve ignoring multiple signature error status codes when installing or verifying collections. A space-separated list of error codes can follow --ignore-signature-status-codes in addition to specifying --ignore-signature-status-code multiple times (for example, ``--ignore-signature-status-codes NO_PUBKEY UNEXPECTED``). - ansible-galaxy - Remove internal configuration argument ``v3`` (ansible/ansible#80721) - ansible-galaxy - add note to the collection dependency resolver error message about pre-releases if ``--pre`` was not provided (ansible/ansible#80048). - ansible-galaxy - used to crash out with a "Errno 20 Not a directory" error when extracting files from a role when hitting a file with an illegal name (ansible/ansible#81553). Now it gives a warning identifying the culprit file and the rule violation (e.g., ``my$class.jar`` has a ``$`` in the name) before crashing out, giving the user a chance to remove the invalid file and try again. (ansible/ansible#81555). - ansible-test - Add Alpine 3.18 to remotes - ansible-test - Add Fedora 38 container. - ansible-test - Add Fedora 38 remote. - ansible-test - Add FreeBSD 13.2 remote. - ansible-test - Add new pylint checker for new ``# deprecated:`` comments within code to trigger errors when time to remove code that has no user facing deprecation message. Only supported in ansible-core, not collections. - ansible-test - Add support for RHEL 8.8 remotes. - ansible-test - Add support for RHEL 9.2 remotes. - ansible-test - Add support for testing with Python 3.12. - ansible-test - Allow float values for the ``--timeout`` option to the ``env`` command. This simplifies testing. - ansible-test - Enable ``thread`` code coverage in addition to the existing ``multiprocessing`` coverage. - ansible-test - Make Python 3.12 the default version used in the ``base`` and ``default`` containers. - ansible-test - RHEL 8.8 provisioning can now be used with the ``--python 3.11`` option. - ansible-test - RHEL 9.2 provisioning can now be used with the ``--python 3.11`` option. - ansible-test - Refactored ``env`` command logic and timeout handling. - ansible-test - Remove Fedora 37 remote support. - ansible-test - Remove Fedora 37 test container. - ansible-test - Remove Python 3.8 and 3.9 from RHEL 8.8. - ansible-test - Remove obsolete embedded script for configuring WinRM on Windows remotes. - ansible-test - Removed Ubuntu 20.04 LTS image from the `--remote` option. - ansible-test - Removed `freebsd/12.4` remote. - ansible-test - Removed `freebsd/13.1` remote. - ansible-test - Removed test remotes: rhel/8.7, rhel/9.1 - ansible-test - Removed the deprecated ``--docker-no-pull`` option. - ansible-test - Removed the deprecated ``--no-pip-check`` option. - ansible-test - Removed the deprecated ``foreman`` test plugin. - ansible-test - Removed the deprecated ``govcsim`` support from the ``vcenter`` test plugin. - ansible-test - Replace the ``pytest-forked`` pytest plugin with a custom plugin. - ansible-test - The ``no-get-exception`` sanity test is now limited to plugins in collections. Previously any Python file in a collection was checked for ``get_exception`` usage. - ansible-test - The ``replace-urlopen`` sanity test is now limited to plugins in collections. Previously any Python file in a collection was checked for ``urlopen`` usage. - ansible-test - The ``use-compat-six`` sanity test is now limited to plugins in collections. Previously any Python file in a collection was checked for ``six`` usage. - ansible-test - The openSUSE test container has been updated to openSUSE Leap 15.5. - ansible-test - Update pip to ``23.1.2`` and setuptools to ``67.7.2``. - ansible-test - Update the ``default`` containers. - ansible-test - Update the ``nios-test-container`` to version 2.0.0, which supports API version 2.9. - ansible-test - Update the logic used to detect when ``ansible-test`` is running from source. - ansible-test - Updated the CloudStack test container to version 1.6.1. - ansible-test - Updated the distro test containers to version 6.3.0 to include coverage 7.3.2 for Python 3.8+. The alpine3 container is now based on 3.18 instead of 3.17 and includes Python 3.11 instead of Python 3.10. - ansible-test - Use ``datetime.datetime.now`` with ``tz`` specified instead of ``datetime.datetime.utcnow``. - ansible-test - Use a context manager to perform cleanup at exit instead of using the built-in ``atexit`` module. - ansible-test - When invoking ``sleep`` in containers during container setup, the ``env`` command is used to avoid invoking the shell builtin, if present. - ansible-test - remove Alpine 3.17 from remotes - ansible-test — Python 3.8–3.12 will use ``coverage`` v7.3.2. - ansible-test — ``coverage`` v6.5.0 is to be used only under Python 3.7. - ansible-vault create: Now raises an error when opening the editor without tty. The flag --skip-tty-check restores previous behaviour. - ansible_user_module - tweaked macos user defaults to reflect expected defaults (ansible/ansible#44316) - apt - return calculated diff while running apt clean operation. - blockinfile - add append_newline and prepend_newline options (ansible/ansible#80835). - cli - Added short option '-J' for asking for vault password (ansible/ansible#80523). - command - Add option ``expand_argument_vars`` to disable argument expansion and use literal values - ansible/ansible#54162 - config lookup new option show_origin to also return the origin of a configuration value. - display methods for warning and deprecation are now proxied to main process when issued from a fork. This allows for the deduplication of warnings and deprecations to work globally. - dnf5 - enable environment groups installation testing in CI as its support was added. - dnf5 - enable now implemented ``cacheonly`` functionality - executor now skips persistent connection when it detects an action that does not require a connection. - find module - Add ability to filter based on modes - gather_facts now will use gather_timeout setting to limit parallel execution of modules that do not themselves use gather_timeout. - group - remove extraneous warning shown when user does not exist (ansible/ansible#77049). - include_vars - os.walk now follows symbolic links when traversing directories (ansible/ansible#80460) - module compression is now sourced directly via config, bypassing play_context possibly stale values. - reboot - show last error message in verbose logs (ansible/ansible#81574). - service_facts now returns more info for rcctl managed systesm (OpenBSD). - tasks - the ``retries`` keyword can be specified without ``until`` in which case the task is retried until it succeeds but at most ``retries`` times (ansible/ansible#20802) - user - add new option ``password_expire_warn`` (supported on Linux only) to set the number of days of warning before a password change is required (ansible/ansible#79882). - yum_repository - Align module documentation with parameters Breaking Changes / Porting Guide -------------------------------- - Any plugin using the config system and the `cli` entry to use the `timeout` from the command line, will see the value change if the use had configured it in any of the lower precedence methods. If relying on this behaviour to consume the global/generic timeout from the DEFAULT_TIMEOUT constant, please consult the documentation on plugin configuration to add the overlaping entries. - ansible-test - Test plugins that rely on containers no longer support reusing running containers. The previous behavior was an undocumented, untested feature. - service module will not permanently configure variables/flags for openbsd when doing enable/disable operation anymore, this module was never meant to do this type of work, just to manage the service state itself. A rcctl_config or similar module should be created and used instead. Deprecated Features ------------------- - Deprecated ini config option ``collections_paths``, use the singular form ``collections_path`` instead - Deprecated the env var ``ANSIBLE_COLLECTIONS_PATHS``, use the singular form ``ANSIBLE_COLLECTIONS_PATH`` instead - Old style vars plugins which use the entrypoints `get_host_vars` or `get_group_vars` are deprecated. The plugin should be updated to inherit from `BaseVarsPlugin` and define a `get_vars` method as the entrypoint. - Support for Windows Server 2012 and 2012 R2 has been removed as the support end of life from Microsoft is October 10th 2023. These versions of Windows will no longer be tested in this Ansible release and it cannot be guaranteed that they will continue to work going forward. - ``STRING_CONVERSION_ACTION`` config option is deprecated as it is no longer used in the Ansible Core code base. - the 'smart' option for setting a connection plugin is being removed as it's main purpose (choosing between ssh and paramiko) is now irrelevant. - vault and unfault filters - the undocumented ``vaultid`` parameter is deprecated and will be removed in ansible-core 2.20. Use ``vault_id`` instead. - yum_repository - deprecated parameter 'keepcache' (ansible/ansible#78693). Removed Features (previously deprecated) ---------------------------------------- - ActionBase - remove deprecated ``_remote_checksum`` method - PlayIterator - remove deprecated ``cache_block_tasks`` and ``get_original_task`` methods - Remove deprecated ``FileLock`` class - Removed Python 3.9 as a supported version on the controller. Python 3.10 or newer is required. - Removed ``include`` which has been deprecated in Ansible 2.12. Use ``include_tasks`` or ``import_tasks`` instead. - ``Templar`` - remove deprecated ``shared_loader_obj`` parameter of ``__init__`` - ``fetch_url`` - remove auto disabling ``decompress`` when gzip is not available - ``get_action_args_with_defaults`` - remove deprecated ``redirected_names`` method parameter - ansible-test - Removed support for the remote Windows targets 2012 and 2012-R2 - inventory_cache - remove deprecated ``default.fact_caching_prefix`` ini configuration option, use ``defaults.fact_caching_prefix`` instead. - module_utils/basic.py - Removed Python 3.5 as a supported remote version. Python 2.7 or Python 3.6+ is now required. - stat - removed unused `get_md5` parameter. Security Fixes -------------- - ansible-galaxy - Prevent roles from using symlinks to overwrite files outside of the installation directory (CVE-2023-5115) Bugfixes -------- - Allow for searching handler subdir for included task via include_role (ansible/ansible#81722) - AnsibleModule.run_command - Only use selectors when needed, and rely on Python stdlib subprocess for the simple task of collecting stdout/stderr when prompt matching is not required. - Cache host_group_vars after instantiating it once and limit the amount of repetitive work it needs to do every time it runs. - Call PluginLoader.all() once for vars plugins, and load vars plugins that run automatically or are enabled specifically by name subsequently. - Display - Defensively configure writing to stdout and stderr with a custom encoding error handler that will replace invalid characters while providing a deprecation warning that non-utf8 text will result in an error in a future version. - Exclude internal options from man pages and docs. - Fix ``ansible-config init`` man page option indentation. - Fix ``ast`` deprecation warnings for ``Str`` and ``value.s`` when using Python 3.12. - Fix ``run_once`` being incorrectly interpreted on handlers (ansible/ansible#81666) - Fix exceptions caused by various inputs when performing arg splitting or parsing key/value pairs. Resolves issue ansible/ansible#46379 and issue ansible/ansible#61497 - Fix incorrect parsing of multi-line Jinja2 blocks when performing arg splitting or parsing key/value pairs. - Fix post-validating looped task fields so the strategy uses the correct values after task execution. - Fixed `pip` module failure in case of usage quotes for `virtualenv_command` option for the venv command. (ansible/ansible#76372) - From issue ansible/ansible#80880, when notifying a handler from another handler, handler notifications must be registered immediately as the flush_handler call is not recursive. - Import ``FILE_ATTRIBUTES`` from ``ansible.module_utils.common.file`` in ``ansible.module_utils.basic`` instead of defining it twice. - Inventory scripts parser not treat exception when getting hostsvar (ansible/ansible#81103) - On Python 3 use datetime methods ``fromtimestamp`` and ``now`` with UTC timezone instead of ``utcfromtimestamp`` and ``utcnow``, which are deprecated in Python 3.12. - PluginLoader - fix Jinja plugin performance issues (ansible/ansible#79652) - PowerShell - Remove some code which is no longer valid for dotnet 5+ - Prevent running same handler multiple times when included via ``include_role`` (ansible/ansible#73643) - Prompting - add a short sleep between polling for user input to reduce CPU consumption (ansible/ansible#81516). - Properly disable ``jinja2_native`` in the template module when jinja2 override is used in the template (ansible/ansible#80605) - Properly template tags in parent blocks (ansible/ansible#81053) - Remove unreachable parser error for removed ``static`` parameter of ``include_role`` - Replace uses of ``configparser.ConfigParser.readfp()`` which was removed in Python 3.12 with ``configparser.ConfigParser.read_file()`` (ansible/ansible#81656) - Set filters ``intersect``, ``difference``, ``symmetric_difference`` and ``union`` now always return a ``list``, never a ``set``. Previously, a ``set`` would be returned if the inputs were a hashable type such as ``str``, instead of a collection, such as a ``list`` or ``tuple``. - Set filters ``intersect``, ``difference``, ``symmetric_difference`` and ``union`` now use set operations when the given items are hashable. Previously, list operations were performed unless the inputs were a hashable type such as ``str``, instead of a collection, such as a ``list`` or ``tuple``. - Switch result queue from a ``multiprocessing.queues.Queue` to ``multiprocessing.queues.SimpleQueue``, primarily to allow properly handling pickling errors, to prevent an infinite hang waiting for task results - The ``ansible-config init`` command now has a documentation description. - The ``ansible-galaxy collection download`` command now has a documentation description. - The ``ansible-galaxy collection install`` command documentation is now visible (previously hidden by a decorator). - The ``ansible-galaxy collection verify`` command now has a documentation description. - The ``ansible-galaxy role install`` command documentation is now visible (previously hidden by a decorator). - The ``ansible-inventory`` command command now has a documentation description (previously used as the epilog). - The ``hostname`` module now also updates both current and permanent hostname on OpenBSD. Before it only updated the permanent hostname (ansible/ansible#80520). - Update module_utils.urls unit test to work with cryptography >= 41.0.0. - When generating man pages, use ``func`` to find the command function instead of looking it up by the command name. - ``StrategyBase._process_pending_results`` - create a ``Templar`` on demand for templating ``changed_when``/``failed_when``. - ``ansible-galaxy`` now considers all collection paths when identifying which collection requirements are already installed. Use the ``COLLECTIONS_PATHS`` and ``COLLECTIONS_SCAN_SYS_PATHS`` config options to modify these. Previously only the install path was considered when resolving the candidates. The install path will remain the only one potentially modified. (ansible/ansible#79767, ansible/ansible#81163) - ``ansible.module_utils.service`` - ensure binary data transmission in ``daemonize()`` - ``ansible.module_utils.service`` - fix inter-process communication in ``daemonize()`` - ``import_role`` reverts to previous behavior of exporting vars at compile time. - ``pkg_mgr`` - fix the default dnf version detection - ansiballz - Prevent issue where the time on the control host could change part way through building the ansiballz file, potentially causing a pre-1980 date to be used during ansiballz unpacking leading to a zip file error (ansible/ansible#80089) - ansible terminal color settings were incorrectly limited to 16 options via 'choices', removing so all 256 can be accessed. - ansible-console - fix filtering by collection names when a collection search path was set (ansible/ansible#81450). - ansible-galaxy - Enabled the ``data`` tarfile filter during role installation for Python versions that support it. A probing mechanism is used to avoid Python versions with a broken implementation. - ansible-galaxy - Fix issue installing collections containing directories with more than 100 characters on python versions before 3.10.6 - ansible-galaxy - Fix variable type error when installing subdir collections (ansible/ansible#80943) - ansible-galaxy - Provide a better error message when using a requirements file with an invalid format - ansible/ansible#81901 - ansible-galaxy - fix installing collections from directories that have a trailing path separator (ansible/ansible#77803). - ansible-galaxy - fix installing signed collections (ansible/ansible#80648). - ansible-galaxy - reduce API calls to servers by fetching signatures only for final candidates. - ansible-galaxy - started allowing the use of pre-releases for collections that do not have any stable versions published. (ansible/ansible#81606) - ansible-galaxy - started allowing the use of pre-releases for dependencies on any level of the dependency tree that specifically demand exact pre-release versions of collections and not version ranges. (ansible/ansible#81606) - ansible-galaxy collection verify - fix verifying signed collections when the keyring is not configured. - ansible-galaxy info - fix reporting no role found when lookup_role_by_name returns None. - ansible-inventory - index available_hosts for major performance boost when dumping large inventories - ansible-test - Add a ``pylint`` plugin to work around a known issue on Python 3.12. - ansible-test - Add support for ``argcomplete`` version 3. - ansible-test - All containers created by ansible-test now include the current test session ID in their name. This avoids conflicts between concurrent ansible-test invocations using the same container host. - ansible-test - Always use ansible-test managed entry points for ansible-core CLI tools when not running from source. This fixes issues where CLI entry points created during install are not compatible with ansible-test. - ansible-test - Fix a traceback that occurs when attempting to test Ansible source using a different ansible-test. A clear error message is now given when this scenario occurs. - ansible-test - Fix handling of timeouts exceeding one day. - ansible-test - Fix parsing of cgroup entries which contain a ``:`` in the path (ansible/ansible#81977). - ansible-test - Fix several possible tracebacks when using the ``-e`` option with sanity tests. - ansible-test - Fix various cases where the test timeout could expire without terminating the tests. - ansible-test - Include missing ``pylint`` requirements for Python 3.10. - ansible-test - Pre-build a PyYAML wheel before installing requirements to avoid a potential Cython build failure. - ansible-test - Remove redundant warning about missing programs before attempting to execute them. - ansible-test - The ``import`` sanity test now checks the collection loader for remote-only Python support when testing ansible-core. - ansible-test - Unit tests now report warnings generated during test runs. Previously only warnings generated during test collection were reported. - ansible-test - Update ``pylint`` to 2.17.2 to resolve several possible false positives. - ansible-test - Update ``pylint`` to 2.17.3 to resolve several possible false positives. - ansible-test - Update ``pylint`` to version 3.0.1. - ansible-test - Use ``raise ... from ...`` when raising exceptions from within an exception handler. - ansible-test - When bootstrapping remote FreeBSD instances, use the OS packaged ``setuptools`` instead of installing the latest version from PyPI. - ansible-test local change detection - use ``git merge-base <branch> HEAD`` instead of ``git merge-base --fork-point <branch>`` (ansible/ansible#79734). - ansible-vault - fail when the destination file location is not writable before performing encryption (ansible/ansible#81455). - apt - ignore fail_on_autoremove and allow_downgrade parameters when using aptitude (ansible/ansible#77868). - blockinfile - avoid crash with Python 3 if creating the directory fails when ``create=true`` (ansible/ansible#81662). - connection timeouts defined in ansible.cfg will now be properly used, the --timeout cli option was obscuring them by always being set. - copy - print correct destination filename when using `content` and `--diff` (ansible/ansible#79749). - copy unit tests - Fixing "dir all perms" documentation and formatting for easier reading. - core will now also look at the connection plugin to force 'local' interpreter for networking path compatibility as just ansible_network_os could be misleading. - deb822_repository - use http-agent for receiving content (ansible/ansible#80809). - debconf - idempotency in questions with type 'password' (ansible/ansible#47676). - distribution facts - fix Source Mage family mapping - dnf - fix a failure when a package from URI was specified and ``update_only`` was set (ansible/ansible#81376). - dnf5 - Update dnf5 module to handle API change for setting the download directory (ansible/ansible#80887) - dnf5 - Use ``transaction.check_gpg_signatures`` API call to check package signatures AND possibly to recover from when keys are missing. - dnf5 - fix module and package names in the message following failed module respawn attempt - dnf5 - use the logs API to determine transaction problems - dpkg_selections - check if the package exists before performing the selection operation (ansible/ansible#81404). - encrypt - deprecate passlib_or_crypt API (ansible/ansible#55839). - fetch - Handle unreachable errors properly (ansible/ansible#27816) - file modules - Make symbolic modes with X use the computed permission, not original file (ansible/ansible#80128) - file modules - fix validating invalid symbolic modes. - first found lookup has been updated to use the normalized argument parsing (pythonic) matching the documented examples. - first found lookup, fixed an issue with subsequent items clobbering information from previous ones. - first_found lookup now gets 'untemplated' loop entries and handles templating itself as task_executor was removing even 'templatable' entries and breaking functionality. ansible/ansible#70772 - galaxy - check if the target for symlink exists (ansible/ansible#81586). - galaxy - cross check the collection type and collection source (ansible/ansible#79463). - gather_facts parallel option was doing the reverse of what was stated, now it does run modules in parallel when True and serially when False. - handlers - fix ``v2_playbook_on_notify`` callback not being called when notifying handlers - handlers - the ``listen`` keyword can affect only one handler with the same name, the last one defined as it is a case with the ``notify`` keyword (ansible/ansible#81013) - include_role - expose variables from parent roles to role's handlers (ansible/ansible#80459) - inventory_ini - handle SyntaxWarning while parsing ini file in inventory (ansible/ansible#81457). - iptables - remove default rule creation when creating iptables chain to be more similar to the command line utility (ansible/ansible#80256). - lib/ansible/utils/encrypt.py - remove unused private ``_LOCK`` (ansible/ansible#81613) - lookup/url.py - Fix incorrect var/env/ini entry for `force_basic_auth` - man page build - Remove the dependency on the ``docs`` directory for building man pages. - man page build - Sub commands of ``ansible-galaxy role`` and ``ansible-galaxy collection`` are now documented. - module responses - Ensure that module responses are utf-8 adhereing to JSON RFC and expectations of the core code. - module/role argument spec - validate the type for options that are None when the option is required or has a non-None default (ansible/ansible#79656). - modules/user.py - Add check for valid directory when creating new user homedir (allows /dev/null as skeleton) (ansible/ansible#75063) - paramiko_ssh, psrp, and ssh connection plugins - ensure that all values for options that should be strings are actually converted to strings (ansible/ansible#81029). - password_hash - fix salt format for ``crypt`` (only used if ``passlib`` is not installed) for the ``bcrypt`` algorithm. - pep517 build backend - Copy symlinks when copying the source tree. This avoids tracebacks in various scenarios, such as when a venv is present in the source tree. - pep517 build backend - Use the documented ``import_module`` import from ``importlib``. - pip module - Update module to prefer use of the python ``packaging`` and ``importlib.metadata`` modules due to ``pkg_resources`` being deprecated (ansible/ansible#80488) - pkg_mgr.py - Fix `ansible_pkg_mgr` incorrect in TencentOS Server Linux - pkg_mgr.py - Fix `ansible_pkg_mgr` is unknown in Kylin Linux (ansible/ansible#81332) - powershell modules - Only set an rc of 1 if the PowerShell pipeline signaled an error occurred AND there are error records present. Previously it would do so only if the error signal was present without checking the error count. - replace - handle exception when bad escape character is provided in replace (ansible/ansible#79364). - role deduplication - don't deduplicate before a role has had a task run for that particular host (ansible/ansible#81486). - service module, does not permanently configure flags flags on Openbsd when enabling/disabling a service. - service module, enable/disable is not a exclusive action in checkmode anymore. - setup gather_timeout - Fix timeout in get_mounts_facts for linux. - setup module (fact gathering) will now try to be smarter about different versions of facter emitting error when --puppet flag is used w/o puppet. - syntax check - Limit ``--syntax-check`` to ``ansible-playbook`` only, as that is the only CLI affected by this argument (ansible/ansible#80506) - tarfile - handle data filter deprecation warning message for extract and extractall (ansible/ansible#80832). - template - Fix for formatting issues when a template path contains valid jinja/strftime pattern (especially line break one) and using the template path in ansible_managed (ansible/ansible#79129) - templating - In the template action and lookup, use local jinja2 environment overlay overrides instead of mutating the templars environment - templating - prevent setting arbitrary attributes on Jinja2 environments via Jinja2 overrides in templates - templating escape and single var optimization now use correct delimiters when custom ones are provided either via task or template header. - unarchive - fix unarchiving sources that are copied to the remote node using a relative temporory directory path (ansible/ansible#80710). - uri - fix search for JSON type to include complex strings containing '+' - uri/urls - Add compat function to handle the ability to parse the filename from a Content-Disposition header (ansible/ansible#81806) - urls.py - fixed cert_file and key_file parameters when running on Python 3.12 - ansible/ansible#80490 - user - set expiration value correctly when unable to retrieve the current value from the system (ansible/ansible#71916) - validate-modules sanity test - replace semantic markup parsing and validating code with the code from `antsibull-docs-parser 0.2.0 <https://github.com/ansible-community/antsibull-docs-parser/releases/tag/0.2.0>`__ (ansible/ansible#80406). - vars_prompt - internally convert the ``unsafe`` value to ``bool`` - vault and unvault filters now properly take ``vault_id`` parameter. - win_fetch - Add support for using file with wildcards in file name. (ansible/ansible#73128) - winrm - Better handle send input failures when communicating with hosts under load
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
I recently uploaded my first collection to Ansible Galaxy 🎉
Unfortunately, I am experiencing some strange behavior which I believe is related to
requirements.yml.ansible-galaxy collection install o0_o.hostresults in:It appears to be trying to install itself as a dependency, but this is not reflected in my
requirements.ymlfile.Most confusingly, specifying either version or installing from a tarball works as expected.
Each of the following will complete without an error:
Issue Type
Bug Report
Component Name
requirements.yml
Ansible Version
Configuration
OS / Environment
macOS
Steps to Reproduce
Expected Results
It should install successfully with dependencies.
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: