OS network import profile (CONFIG/network/my-network) ignores [ipv6] method=disabled during first boot core installation

Installation
1

during the initial onboarding/first boot phase of Home Assistant OS (tested with HAOS 17.3 and 18.0 on Raspberry Pi 4), the Supervisor completely ignores the method=disabled directive under the [ipv6] section supplied via the USB/Boot-partition network import profile (CONFIG/network/my-network).

Steps to reproduce

  1. Flash a clean HAOS image onto an SD card.
  2. Create an onboarding network profile under CONFIG/network/my-network with [ipv6] method=disabled and a static IPv4 configuration.
  3. Boot the Pi on a dual-stack/DS-Lite network topology where IPv6 connectivity to GitHub/Docker Hub is broken or intermittent
  4. The initial version fetch and Core image download hang indefinitely.

Logs

The supervisor logs show constant NetworkManager and D-Bus cycling errors, explicitly trying to contact DNS servers via IPv6:
ERROR (MainThread) [supervisor.host.network] No network D-Bus connection available
aiodns.error.DNSError: (11, 'Could not contact DNS servers')
OSError: [Errno None] Could not contact DNS servers (showing resolved IPv6 addresses like 2001:4860:4860::8888 in the fallback pool).

Expected behavior

The Supervisor and its pre-onboarding connectivity check scripts must strictly respect the imported NetworkManager profile (method=disabled) from the very first second of the boot sequence, instead of forcing dual-stack lookups before the network profile is fully applied on the host level.

2

If you think you have found an issue, please report it here: