Add ensure_beaker_ip_on to fix unapplied static IPs (EL10/vagrant)

[silug]

Problem

Vagrant configures static private-network IPs on RedHat-family guests by writing legacy ifcfg files, which EL10 no longer supports. The interface silently falls back to NetworkManager DHCP with an arbitrary address, so everything that targets the Beaker-recorded host[:ip] (cross-SUT traffic, direct Net::SSH logins, NFS mounts, log forwarding) fails with No route to host.

This is the root cause of the almalinux10 acceptance failures across the open cleanup PRs (rsyslog, simp_snmpd, tlog, autofs, nfs, simp_nfs, simp_gitlab, libreswan).

Fix

New ensure_beaker_ip_on(hosts), run automatically in the global before(:all) alongside activate_interfaces:

• Skips hosts whose host[:ip] is already assigned (cheap no-op on healthy platforms)
• Finds the interface attached to the expected network (subnet match against live ip -o -4 addr)
• Re-applies the expected address via nmcli connection modify ... ipv4.method manual ... ipv4.never-default yes (reboot-safe, matches Vagrant's static-network semantics — no gateway/default-route pollution)
• Falls back to a runtime-only ip addr add when NetworkManager isn't managing the interface
• Honors the existing BEAKER_no_fix_interfaces escape hatch

Validation

pupmod-simp-tlog beaker:suites[default,almalinux10] (vagrant_libvirt): 13 examples / 1 failure → 66 examples / 0 failures, with the remediation visible in the log:

-- FIXING: almalinux10 expected IP 10.254.103.152 but 'eth1' has 10.254.12.227

Unit suite: 23 examples, 0 failures; rubocop clean.

Release note for consumption

simp-rake-helpers ~> 5.24 currently pins simp-beaker-helpers ~> 2.0, and module Gemfiles default to '~> 2.0.0' — so module CI cannot consume a 3.x release today. Options: relax the rake-helpers pin, or backport this to a 2.0.6 release (module Gemfiles' ~> 2.0.0 would pick a 2.0.x up automatically).

🤖 Generated with Claude Code