mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-11-19 17:02:15 +00:00
fix(template): an IPv6 node gets an AutoYaST profile that YaST refuses
_autoyast_network6 emitted dhcp_resolv in the dns block of the networking section. The AutoYaST schema of Leap 15.6 does not accept that element, and one element it refuses invalidates the whole profile: YaST reported "Extra element networking in interleave", then "A profile for this machine could not be found or retrieved", and the installation stopped. dhcp_resolv says whether DHCP may overwrite resolv.conf. The section configures the node statically, so there is no DHCP to keep away from resolv.conf. Measured with the schema the installer ships, /usr/share/YaST2/schema/autoyast/ rng/profile.rng: the profile failed to validate at the networking element, and removing dhcp_resolv alone made it validate. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
This commit is contained in:
@@ -1390,7 +1390,10 @@ sub _autoyast_network6 {
|
||||
{
|
||||
'domain' => ["$domain"],
|
||||
'dhcp_hostname' => [ { 'content' => 'false', 'config:type' => 'boolean' } ],
|
||||
'dhcp_resolv' => [ { 'content' => 'false', 'config:type' => 'boolean' } ],
|
||||
# dhcp_resolv says whether DHCP may overwrite resolv.conf. The
|
||||
# AutoYaST schema of Leap 15.6 refuses it, and one element it
|
||||
# refuses makes YaST reject the whole profile. This section is
|
||||
# static, so no DHCP can touch resolv.conf anyway.
|
||||
'nameservers' => [ { 'config:type' => 'list', 'nameserver' => [@nameserversIP] } ],
|
||||
}
|
||||
],
|
||||
|
||||
Reference in New Issue
Block a user