#1621 Ensuring ansible automation in place can manage/control el10 nodes
Closed: Fixed by arrfab. Opened by arrfab.

As our current management infra (ansible) is still hosted on RHEL9, we should ensure that it would be able to properly manage el10 systems (Stream10/RHEL10) as we already found one issue (details below) so opening this ticket so that everybody can track WIP about it


Metadata Update from @arrfab:
- Issue tagged with: centos-common-infra, doc, el10-readyness, high-gain, high-trouble, investigation

Metadata Update from @arrfab:
- Issue assigned to arrfab

First found issue : ansible-core 2.14.x (currently supported/available version on RHEL9 doesn't parse correctly ini format from remote local facts .
More details on https://github.com/ansible/ansible/issues/84824

For found issue above (but more tests coming) we have multiple options :

  • create/report issue for RHEL9 (Jira) : to be done anyway but we can't be sure that it will be backported and so landing in stream9/RHEL9
  • backport that patch ourselves into our own ansible-core rebuild (or "hot-patch" on our ansible host[s] management nodes)
  • modify our own roles to just create from now .fact files into json format instead of ini format

If that's really the only thing that is a problem, I'd still do [1] (for awareness) but go with [3] as that means nothing to backport/maintain forever at our side (and current ansible-core version supports already json and ini format

FWIW, created https://issues.redhat.com/browse/RHEL-83561 for awareness, but already working on step [3] as there isn't a lot to do to convert and so unblock us

Went with plan 3 (converting our .fact file to json format) as it seems it will not be fixed anyway in RHEL9

Metadata Update from @arrfab:
- Issue marked as depending on: #1526

our iptables role has now proper support for el10 and nftables (replacement for iptables) and ansible can easily manage a el10/Stream 10 host.
So closing now this ticket

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata