Bug#1007907: ansible-core: cannot install collecions

Bernhard Bock

unread,

Mar 18, 2022, 8:10:03 AM3/18/22

to

Package: ansible-core
Version: 2.12.3-1
Severity: normal
X-Debbugs-Cc: bern...@bock.nu

Dear Maintainer,

I tried to install a collection and ran into a python stacktrace as included below.
According to my understanding, the Debian version of python3-resolvelib is too new.

For reference, see also https://github.com/ansible-collections/community.digitalocean/issues/132
and https://bugs.gentoo.org/795933

regards,
Bernhard

# ansible-galaxy install -r requirements.yml
...
Starting galaxy collection install process
Process install dependency map
ERROR! Unexpected Exception, this is probably a bug: find_matches() got an unexpected keyword argument 'identifier'
the full traceback was:

Traceback (most recent call last):
File "/usr/bin/ansible-galaxy", line 128, in <module>
exit_code = cli.run()
File "/usr/lib/python3/dist-packages/ansible/cli/galaxy.py", line 569, in run
return context.CLIARGS['func']()
File "/usr/lib/python3/dist-packages/ansible/cli/galaxy.py", line 86, in method_wrapper
return wrapped_method(*args, **kwargs)
File "/usr/lib/python3/dist-packages/ansible/cli/galaxy.py", line 1203, in execute_install
self._execute_install_collection(
File "/usr/lib/python3/dist-packages/ansible/cli/galaxy.py", line 1230, in _execute_install_collection
install_collections(
File "/usr/lib/python3/dist-packages/ansible/galaxy/collection/__init__.py", line 513, in install_collections
dependency_map = _resolve_depenency_map(
File "/usr/lib/python3/dist-packages/ansible/galaxy/collection/__init__.py", line 1329, in _resolve_depenency_map
return collection_dep_resolver.resolve(
File "/usr/lib/python3/dist-packages/resolvelib/resolvers.py", line 481, in resolve
state = resolution.resolve(requirements, max_rounds=max_rounds)
File "/usr/lib/python3/dist-packages/resolvelib/resolvers.py", line 348, in resolve
self._add_to_criteria(self.state.criteria, r, parent=None)
File "/usr/lib/python3/dist-packages/resolvelib/resolvers.py", line 147, in _add_to_criteria
matches = self._p.find_matches(
TypeError: find_matches() got an unexpected keyword argument 'identifier'

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-rc7-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ansible-core depends on:
ii openssh-client 1:8.9p1-3
ii python3 3.9.8-1
ii python3-cryptography 3.4.8-1
ii python3-distutils 3.9.10-1
ii python3-dnspython 2.2.0-2
ii python3-httplib2 0.20.2-2
ii python3-jinja2 3.0.3-1
ii python3-netaddr 0.8.0-2
ii python3-packaging 21.3-1
ii python3-pycryptodome 3.11.0+dfsg1-3
ii python3-resolvelib 0.8.1-1
ii python3-yaml 5.4.1-1+b1

Versions of packages ansible-core recommends:
ii ansible 5.4.0-1
ii python3-argcomplete 1.12.3-0.1
ii python3-jmespath 0.10.0-1
ii python3-kerberos 1.1.14-3.1+b4
ii python3-libcloud 3.4.1-2
ii python3-selinux 3.3-1+b2
ii python3-winrm 0.3.0-2
ii python3-xmltodict 0.12.0-2

Versions of packages ansible-core suggests:
pn cowsay <none>
pn sshpass <none>

-- no debconf information

Daniele Tricoli

unread,

Mar 22, 2022, 9:50:04 PM3/22/22

to

On Fri, 18 Mar 2022 13:03:13 +0100 Bernhard Bock <bern...@bock.nu> wrote:
> I tried to install a collection and ran into a python stacktrace as included below.
> According to my understanding, the Debian version of python3-resolvelib is too new.
>
> For reference, see also https://github.com/ansible-collections/community.digitalocean/issues/132
> and https://bugs.gentoo.org/795933

I can confirm that the workaround of downgrading python3-resolvelib to 0.5.4-1
solve the issue.

--
Daniele Tricoli 'eriol'
https://mornie.org

signature.asc

Lee Garrett

unread,

Mar 24, 2022, 10:10:04 AM3/24/22

to

Hi,

I can confirm the issue exists, unfortunately there is no simple
solution, as upstream resolvlib does not have a stable API yet. I might
be able to downgrade resolvelib in testing/unstable, as ansible-core
seems to be the only package that currently consumes it. This will
probably get better in the near future when 1.0 is released.

Regards,
Lee

Florian Küpper

unread,

Sep 4, 2022, 9:40:07 PM9/4/22

to

Any news or plans on this ?

Is something blocking progress ?

The fix https://github.com/ansible/ansible/pull/77649 went into devel on Jun 7 ,

... became release candidate on June 20 (https://github.com/ansible/ansible/blob/stable-2.13/changelogs/changelog.yaml#L834)

and is included in the ansible stable releases since 2.13.1 (also june 20) https://github.com/ansible/ansible/blob/stable-2.13/changelogs/changelog.yaml#L779-L782

Since this https://salsa.debian.org/debian/ansible-core/-/blob/master/debian/patches/0008-support-newer-resolvelib.patch is not even in debian yet .. how about a regular update of ansible-core instead ?

Do You need help?