Hide Forgot
Created attachment 557423 [details] eth_with_ip Description of problem: Version-Release number of selected component (if applicable): How reproducible: When attempting to add a VLAN to an HOST's ETH, with already configured IP address - It will not accept the original IP address of the interface for that VLAN. VDSM should know that after adding a Brdige (LN), the original IP of the interface will be lost, and therefore this IPADDR can be used. Steps to Reproduce: 1.via webadmin try to attach a vlan to an eth with already configured IPADDR 2. 3. Actual results: Expected results: Additional info: Trying to create a vlan on eth 3 with IPADDR of eth3 (10.20.20.200) fails: Thread-35982::DEBUG::2012-01-25 11:59:15,588::clientIF::76::vds::(wrapper) [10.35.97.70]::call addNetwork with ('164', '164', '', ['eth3'], {'STP': 'no', 'NETMASK': '255.255.255.0', 'IPADDR': '10.20.20.200'}) {} . . . Thread-35982::ERROR::2012-01-25 11:59:15,632::clientIF::1125::vds::(addNetwork) IP address is already in use If a different IPADDR will be chosen (10.20.20.222) the bridge for that VLAN will be created and the original IPADDR (10.20.20.200) will not be in use in the HOST.
Correct, when validating the IP address, we should discount addresses that are to be deleted.
*** This bug has been marked as a duplicate of bug 787709 ***