Hi Christoph,
On 09/08/2020 10:01, Christoph Biedl wrote:
> Package: ansible
> Version: 2.7.7+dfsg-1
> Severity: normal
>
> Dear Maintainer,
>
> My ansible playbooks heavily rely on the the operation system of the
> managed machine. After upgrading the managed host I noticed the
> "ansible_distribution" and releated are no longer included in the
> facts, resulting in major breakage.
>
>
> The controlling host is still Debian 10 ("buster") a.k.a.
>
> | ii ansible 2.7.7+dfsg-1 all Configuration management,
> deployment, and task execution system
>
>
> The managed host ($h) is unstable, python2 has been removed lately
> (possibly unrelated).
>
> Old facts (pre-upgrade) were gathered using:
>
> | ansible -m setup -i "$h," $h
>
> New facts were gathered using
>
> | ansible -m setup -i "$h," $h -e
> 'ansible_python_interpreter=/usr/bin/python3'
>
> Comparing the output ...
>
> Expected: No relevant changes (just time, memory usage etc.)
>
> Observed:
>
> | "ansible_devices": {
> | (...)
> | },
> | - "ansible_distribution": "Debian",
> | - "ansible_distribution_file_parsed": true,
> | - "ansible_distribution_file_path": "/etc/os-release",
> | - "ansible_distribution_file_variety": "Debian",
> | - "ansible_distribution_major_version": "bullseye/sid",
> | - "ansible_distribution_release": "NA",
> | - "ansible_distribution_version": "bullseye/sid",
> | "ansible_dns": {
> | "nameservers": [
>
> If you can shed some light on this, I'd be glad.
sorry for the late reply, this bug report must have slipped through. I
have one testing VM, and I can reproduce this issue when using python3
on the target. Installing python2 on it and using that will still
produce the wanted facts, so that might be one possible workaround.
I haven't been able to reproduce this issue with ansible 2.10, so I
think it's one of the many python3 bugs they've fixed in between those
releases.
Regards,
Lee
