Set default for use in netplan.yml and wording

[jvonau]

Fixes bug:

Default to False or perhaps move the when: ansible_local.local_facts.systemd_networkd == "enabled" or ansible_local.local_facts.systemd_networkd == "enabled-runtime" to replace when: systemd_networkd_active

Description of changes proposed in this pull request:

Smoke-tested on which OS or OS's:

Mention a team member @username e.g. to help with code review:

[jvonau]

For the record the reason the 2 conditional were 2 parts in the past within detected_network.yml was to tell which one applied while debugging.

[holta]

Is this line no longer sufficient or no longer useful?

iiab/roles/network/defaults/main.yml

Line 86 in b735672

systemd_networkd_active: False

Related:

• PR /usr/local/sbin/netwarn pop-ups (if iiab-network needs to be run) on MATE & RasPiOS with desktop + roles/network refactoring #3318

[jvonau]

Not sufficient when called via 1-Prep and the service is not enabled.

[jvonau]

The only fix noted when clean installing on Ubuntu desktops, in this case Mate, other Ubuntu variants should be the same as they all use NetworkManager as the backend for use with netplan and ship with systemd-networkd present but disabled.

[jvonau]

For the record ./runrole --reinstall network would not be enough to uncover this one as we enable and use systemd-networkd for br0 but out of the box all desktops would have this service disabled, thus I found this one building new images for #3303

[jvonau]

Note: As of today 92 packages should be upgraded post install on the upstream Mate-arm64 image while my images would have these updates baked into the image.

[holta]

Is this PR tested + safe?

[jvonau]

Just build image with this commit in place.. or the builder would puke..

[jvonau]

If that is the only change ship it..