Bug 961382
Summary: | Invalid list of interfaces, two or more network interfaces have the same IP | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Wesley Duffee-Braun <wduffee> |
Component: | ovirt-engine-webadmin-portal | Assignee: | Lior Vernia <lvernia> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | acathrow, bazulay, danken, ecohen, gwatson, iheim, jkt, Rhev-m-bugs |
Target Milestone: | --- | ||
Target Release: | 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | network | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-22 12:07:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wesley Duffee-Braun
2013-05-09 13:58:25 UTC
Lior, Essentially the 'rhevm' network interface did not have vlan tagging enabled (at the Data Center level - the 'rhevm' entry in the 'network' table in the database did not have a 'vlan_id'), yet a vlan-tagged 'rhevm' interface existed as a member of the one bonded interface. Everything was apparently working ok though. They then created a new vlan and when they tried to add it, they got the "Invalid list of interfaces, two or more network interfaces have the same IP" error. This was due to the duplicate interface entries. Once all of the duplicates were removed from the database manually via sql commands, they then got the error "Cannot setup Networks. The following Network Interfaces can have only a single VM Logical Network, or at most one non-VM Logical Network and/or several VLAN Logical Networks: bond0" when trying to add the new vlan again. This was "resolved" by manually adding a 'vlan_id' via an sql command to the 'rhevm' entry in the 'network' table. Once this was done, the new vlan could then be added successfully. Hope this clarifies the situation. If not, please let me know. GFW. Thanks Gordon, You have clarified the situation, I apologize for the delay. The error message concerning the different networks not being able to live together on the same interface is as designed. If 'rhevm' is VLAN-tagged on the hosts, it should also be marked as such in the engine for consistency. However, the duplicate network entries are definitely a bug. Could the customer retrace how these duplicate entries were created? Yours, Lior. Lior, The customer had the 'rhevm' network set on RHEV-M to not use vlan tagging even though it was vlan-tagged on the hosts. They believe that the duplicate entries were created when they attempted to then add a new network. I know I looked at this at the time, but to be honest I don't remember what I saw. I would have to go back and look at this all over again. So, other than what the customer believes caused the problem to occur, I don't have much else to add at this time. Regards, GFW. Closing as I haven't been able to either reproduce the duplication bug or trace its origin in the logs attached to the customer portal ticket - all duplicate entries that appear in the log (there's no mention of 'webcms' in the attached logs) have been created way back in April 2012 and their creation is not logged. All other behavior described above, related to the management network being VLAN-tagged on the hosts but not on the engine, doesn't seem like a bug. |