Bug 1266189 - RHEV Manager showing 2 unique configurations for a single bond connection
Summary: RHEV Manager showing 2 unique configurations for a single bond connection
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Dan Kenigsberg
QA Contact: Aharon Canan
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 17:51 UTC by emahoney
Modified: 2023-09-14 03:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-30 13:02:24 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot showing 2 external and 1 rhevm connections on a bond (82.07 KB, image/png)
2015-09-24 17:51 UTC, emahoney
no flags Details
Screenshot showing 1 external and 1 rhevm connection on the same bond (123.29 KB, image/png)
2015-09-24 17:52 UTC, emahoney
no flags Details

Description emahoney 2015-09-24 17:51:35 UTC
Created attachment 1076651 [details]
Screenshot showing 2 external and 1 rhevm connections on a bond

Description of problem:

We are running into one of 3 errors each time we try to modify a bond connection on ANY of his hosts.

Here is our situation:

    -In the manager, when selecting a host, we see 2 external and 1 rhevm connection on a bond0 interface
    -When we select "setup host networks' we only see 1 external and 1 rhevm connection
    -This manager thinks that the network is in sync (thus the source of our confusion)

When we try to 'sync' the network (and VLAN tags associated to it) we have recieved 3 different messages:

    -Invalid operation, an out-of-sync network can only be detached. (Great, so the interface status says sync'd and this message says out-of-sync)
    -"Invalid list of interfaces, two or more networks have the same IP"
    -Unhandled exception (Detailed at the end of this note)

Version-Release number of selected component (if applicable):

Host:
Red Hat Enterprise Linux Server release 6.6 (Santiago)

Manager:
rhevm-3.5.3.1-1.4.el6ev.noarch

How reproducible:
Making a game-plan right now to replicate the VLAN tagging that could be the reason for this issue.

Steps to Reproduce:
1. WIP
2.
3.

Actual results:
3 connections in a bond when 
***See screenshots***

Expected results:
2 connections in a bond

Additional info:

Comment 1 emahoney 2015-09-24 17:52:51 UTC
Created attachment 1076652 [details]
Screenshot showing 1 external and 1 rhevm connection on the same bond

Comment 2 emahoney 2015-09-24 17:57:41 UTC
Below is the unhandled exception


Thread-15339::ERROR::2015-09-24 09:32:29,308::__init__::506::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 501, in _serveRequest
    res = method(**params)
  File "/usr/share/vdsm/rpc/Bridge.py", line 271, in _dynamicMethod
    result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 1398, in setupNetworks
    supervdsm.getProxy().setupNetworks(networks, bondings, options)
  File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>
    **kwargs)
  File "<string>", line 2, in setupNetworks
  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
    raise convert_to_error(kind, result)
AssertionError
Thread-15339::DEBUG::2015-09-24 09:32:29,308::stompReactor::163::yajsonrpc.StompServer::(send) Sending response

Comment 3 Dan Kenigsberg 2015-10-21 09:33:38 UTC
The interesting log is supervdsm.log. Please attach.

Comment 4 emahoney 2015-10-30 13:02:24 UTC
Customer decided to rebuild their environment. 

This BZ can be closed.

Evan

Comment 5 Red Hat Bugzilla 2023-09-14 03:05:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.