Daniel Hilst 5ce5edf24b fix(debian): nodes with no xcatmaster get no boot config at all ...

The subiquity path resolved $instserver with getipaddr and `next`ed the node
when that returned nothing. For a node whose noderes.xcatmaster is unset,
$instserver is the literal '!myipfn!' -- a placeholder that pxe.pm:176 and
grub2.pm:129 substitute with my_ip_facing($node) when they write the boot
config. Resolving it as a name always fails, so those nodes went from a working
numeric nfsroot to no boot config and a "Could not resolve the install server"
error.

noderes.5.rst:125 documents an unset xcatmaster as supported, and anaconda.pm
and sles.pm both already guard the placeholder with
`unless ($instserver eq '!myipfn!')`.

Exempt the placeholder, keeping the guard for a real name that does not
resolve -- klibc's nfsmount still cannot resolve one of those, which is what
the original commit was for.

The decision moves into subiquity_nfsroot_server(), taking the resolver as an
optional argument, so it can be driven directly instead of through a routine
that needs a management node.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>

2026-09-01 18:47:45 -03:00

..

perl/xCAT

fix(xcat-core): do not add a second syncfiles when the node already defers it

2026-08-28 09:45:56 -03:00

xcat

fix(debian): nodes with no xcatmaster get no boot config at all

2026-09-01 18:47:45 -03:00