network-flush: reset autoconnect-priority to zero

network-flush: reset autoconnect-priority to zero (#65)

With older dracut, where NetworkManager does not run as a daemon
and with dbus, the dracut module we have will not work to disable
autoconnect for the connections created within the initramfs, which
may be a problem as after the network flush, NM will activate the
connection with the higher priority, and the initramfs connection
may be it.

Some connections are created with negative priority, by e.g. the
Anaconda installer, which may be a problem in this situation. To
work around this issue, we now reset the autoconnect priority of
the connections to zero.

Add dracut module for disabling autoconnect within initrd

Add dracut module for disabling autoconnect within initrd (#64)

• Add whitespaces between the values in omit_dracutmodules dracut conf

This fixes the following issue:

dracut: WARNING: +=" ": should have surrounding white spaces!
dracut: WARNING: This will lead to unwanted side effects! Please fix the configuration file.

• Add dracut module for disabling autoconnect within initrd

The network connection created during the initramfs for unlocking the
device may conflict with the actual system connection later on, when
the system attempts to configure the network as per the regular
configuration, after the boot process has completed.

To prevent this situation, we now deploy a dracut module to disable
autoconnect of the network connectons that are active during the
initramfs.

Add network flushing before setting up network (#58)

Add network flushing before setting up network (#58)

This should allow for using the nbde_client role with machines that use
static IP configurations, as network flushing should undo the network
setup done at the initramfs, allowing the system to use its regular
configuration.

Approach based on the answers posted here:
https://unix.stackexchange.com/questions/506331/networkmanager-doesnt-change-ip-address-when-dracut-cmdline-provided-static-ip/541108

remove recursive role symlink in tests/roles

change recursive role symlink to individual role dir symlinks (#57)

Signed-off-by: Rich Megginson [email protected]

bump tox-lsr version to 2.8.3 (#59)

Signed-off-by: Rich Megginson [email protected]

add regenerate-all to the dracut command; test with ansible 2.12

use tox-lsr version 2.5.1 (#52)

This version removes support for molecule until we can figure out
what to do about molecule. This should make all of the tox tests
pass (except for python 2.6).

make role work with ansible-core-2.11 ansible-lint and ansible-test (#53)

add regenerate-all to the dracut command (#48)

RHEL8 doc - added --regenerate-all to RedHat 9 according to the new changes in RHEL doc

support python 39, ansible-core 2.12, ansible-plugin-scan (#54)

also fix some linter issues

update tox-lsr version to 2.7.1 (#55)

update the tox-lsr version used in github actions tox CI
to 2.7.1

The only difference between this an 2.7.0 is that Ansible 2.12
is now GA.

Signed-off-by: Rich Megginson [email protected]

drop support for ansible 2.8

Drop support for Ansible 2.8 by bumping the Ansible version to 2.9

min_ansible_version is now 2.9
Bug 1989197 - drop support for Ansible 2.8
https://bugzilla.redhat.com/show_bug.cgi?id=1989197

fix python black formatting

fix python black formatting errors (#50)

Fix lint issues; support EL 9 managed hosts

Fix lint issues

support EL 9 managed hosts

support jinja 2.7

support jinja 2.7

Changes to support conversion to collections

This contains changes to support conversion to collection as well as some tox/travis fixes. No functionality changes.