I've noticed a issue in foreman when assigning IP space using the "Internal DB". We currently want both ipv4 and ipv6 space to match when assigned. Something like this.

10.0.0.230
XXXX:XXX:XXX:5::0:230

If you set the range of ipv4 space to 10.0.0.230 to 10.0.0.250 and ipv6 XXXX:XXX:XXX:5::0:230 to XXXX:XXX:XXX:5::0:250 when you build a VM you'll get these 2 assigned if building a VM.

10.0.0.230
XXXX:XXX:XXX:5::0:231

(v4 is .230, v6 is :231)

Now, if you build baremetal it works and assigns them simlarly (10.0.0.230 XXXX:XXX:XXX:5::0:230).

Since we're not building a lot of baremetal machines I set the ipv4 value to 10.0.0.231 to 10.0.0.250 and it allows us to work around it (it assigns in proper sequence). HOWEVER this breaks baremetal and you have to manually correct it. Same for "clone" versions of host creations.

This seems to be an issue with 1.15 and 1.16 (probably earlier also).

It would be nice if this could be set to assign the space the same across all methods so you can set specific ranges for ipv4 and ipv6 and they match consistently.