Bug #6787
open
Turn off the validation on ip addresses
Description
The cases that the validation prevents doing:
1. 2 isolated networks with smart-proxy managed services (because for
various reasons it's not possible to have the global smart proxy).
2. managing more identic livirt instances with one foreman (NAT networks with
the same mask).
Is there any reason why the IP uniqueness is required anyway?
Updated by Ivan Necas over 9 years ago
- Related to Feature #6444: Add ancestry NICs and allow interfaces with same MAC added
Updated by Dominic Cleal over 9 years ago
- Category set to Network
If you have multiple identical subnets, then you'll hit uniqueness issues on those too (similar to issue #3513), so just removing IP address validation isn't enough.
IP addresses are used to identify hosts during unattended installation, so are meant to be unique.
Updated by Dominic Cleal over 9 years ago
- Related to Bug #3513: Foreman assigns wrong VPC when multiple VPCs have same subnets added
Updated by Ivan Necas over 9 years ago
The token-based identification is now set as default. What about deprecating the ip-based identification? Is there any case it's still not an option? If it is, is it mainstream enough to keep the uniqueness enforced. One posibility would be to enable the validation only when the ip-based identification is used (not saying that I would like that, but it would be better, than the current state)
Updated by Marek Hulán over 9 years ago
And probably disallow IP-based identification unless all IPs are unique. Or just warn user that it's limitation of IP-based identification and leave conflict up to him/her. I'd vote for validations.