Hi,
On Mon, Oct 26, 2020 at 09:47:27PM +0100, Till Maas wrote:
Am Mo., 26. Okt. 2020 um 19:29 Uhr schrieb Rich Megginson
<rmeggins(a)redhat.com>:
>
> The short answer is no, we cannot drop support for ansible 2.8 yet (upstream, it is
still marked as maintained for security fixes, which means we should still support it;
downstream for Red Hat customers, we will still be supporting 2.8 for the foreseeable
future).
>
> That being said - let's see if we can fix your problems - see below
>
> On 10/24/20 2:32 AM, Gris Ge wrote:
>
> Hi,
>
> According to [ansible lifecyle][1], the ansible 2.8 is security fixes
> only.
>
> And ansible 2.8 already breaks our CI on Fedora 32 when
> trying to collect service facts:
>
>
https://github.com/ansible/ansible/issues/69302
>
>
> I thought we had some sort of workaround for this? Perhaps Till remembers?
Maybe it just went away because we did not test with Ansible 2.8
anymore back then. The discussion/idea to remove the services_facts
module happened here:
https://github.com/linux-system-roles/network/pull/219
As we can specify the minimum ansible version per image in CI, I suggest
to set it to 2.9 for Fedora images.
(It will solve this service_facts issue but not the other one with
module_utils import.)
P.