Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.