Interfaces.subnet6 is not defined for location

When trying to auto-provision a server in foreman, we get the error message “interfaces.subnet6 is not defined for location”. If i disable the auto-provision rule, leaving it in discovery, there does not appear to be any reference to ipv6. We only have 1 ipv6 subnet defined in foreman (configured as EUI-64), but it belongs to a different location.

Via foreman-rake console, the discovered host reports subnet6 is nil.

If I add the location to the ipv6 subnet, it does provision, and foreman-rake console reports it having a subnet6, but it doesn’t actually have an ipv6 address. It doesn’t even create an AAAA record, so it must be “failing” to pick the ipv6 as well.

I don’t understand where foreman is getting the idea to place it in this ipv6 subnet. It seems to be rather exclusive to a very limited set of servers, but I haven’t found anything that separates these from servers that work.

Expected outcome:
Foreman should not be attempting to assign an IP to this subnet.

Foreman and Proxy versions:

Foreman and Proxy plugin versions:
Discovery 7.0.0

Other relevant data:
2018-08-08 07:34:57 57445926 [app] [I] Match found for host mac246e96e10612 (443278) rule [redacted] (5320)
2018-08-08 07:34:58 57445926 [templates] [I] Rendering template ‘Unnamed’
2018-08-08 07:34:59 57445926 [app] [D] Observed before_validation hook on [redacted]
2018-08-08 07:34:59 57445926 [app] [D] Running 1 hooks for Host::Managed#before_validation
2018-08-08 07:35:00 57445926 [app] [D] Suggesting ip for Test IPv6 Provisioning Network based on mac ‘’ (EUI-64).
2018-08-08 07:35:01 57445926 [app] [D] Comparing [“24:6e:96:e1:06:12”, “”, “”] == [“24:6e:96:e1:06:12”, “”, “”]
2018-08-08 07:35:01 57445926 [app] [D] Comparing [“24:6e:96:e1:06:12”, “”, “”] == [“24:6e:96:e1:06:12”, “”, “”]
2018-08-08 07:35:03 57445926 [app] [W] Failed to auto provision host [redacted]: Subnet6 is not defined for host’s location.