Re: [Users] Error: The following Network Interfaces were specified more than once:
On 29/01/14 17:18, Alan Murrell wrote: Quoting Lior Vernia lver...@redhat.com: It's a quirk of oVirt at the moment :) The interface state as shown in the GUI currently has very little to do with whether there's connectivity on a network. There should be an open RFE for connectivity OK, so at this point it is a cosmetic issue as opposed to a functional one? It's a little of both. It is a cosmetic issue if you're looking to see the link state, functional if you were expecting it to tell you whether there's layer 3 connectivity. -Alan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Error: The following Network Interfaces were specified more than once:
Please run: vdsClient -s 0 getVdsCaps And paste the output. If this is caused by what I think is causing it, then this bug was fixed during the 3.4 development cycle and is available in the 3.4 beta release. (It affects dummy devices and VLANs). Assaf Muller, Cloud Networking Engineer Red Hat - Original Message - From: Alan Murrell li...@murrell.ca To: users@ovirt.org Sent: Wednesday, January 29, 2014 10:27:21 AM Subject: [Users] Error: The following Network Interfaces were specified more than once: I have noticed what seems to me to be a quirk, but wanted to see if this is correct behaviour, or perhaps my configuration. I am running a test install ov oVirt 3.3.2 in an all-in-one install. My test box only has one physical NIC, so I am using that for management/external network access, and I have create a dummy interface called dummy_0 to be used for the VMs. I created four networks, each assigned their own VLAN (I am wanted to simulate a real-world . I added the first network (VLAN001) to dummy_0 with no problem (I was able to save the configuration). The system created the dummy_0.1. When I tried to add another network (VLAN002) to dummy_0 and save it, I got the following error: --- START --- Error while executing action: local_host: Cannot setup Networks. The following Network Interfaces were specified more than once: dummy_0.1. --- END --- I found that in the Setup Host Network if I dragged VLAN001 off dummy_0 to the right under Required, and left VLAN002 on dummy_0, I could save it, and VLAN001 appeared to remain active on the host. Indeed, when I went back into Setup Host Network, both VLAN001 and VLAN002 were showing up on dummy_0. However, if I highlight VLAN002 under Networks and click on the Hosts tab, the Network Interface is showing a red down arrow, indicating it is not up. The Network Interface for VLAN001 is a green up arrow. I have refreshed several times and at this point in time, have left it for almost thirty minutes, but it remains as a red down arrow. The same is true for the other two networks I tried adding: I was able to add them as above, but they are also showing a red down arrow. My questions: 1.) Is doing what I had to do to add additional networks to an interface normal, or is it a quirk of using a dummy interface? 2.) Any ideas why my additional networks are showing a red down arrow? Again, maybe a quirk of using a dummy interface? I am going to leave it overnight and see what happens (maybe some background process needs to run??), but if that does not work, I am sure I can scrounge up another NIC in the next couple of days and install it into my test server to see if it does the same thing. Thanks, in advance. -Alan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Error: The following Network Interfaces were specified more than once:
On 29/01/14 10:27, Alan Murrell wrote: I have noticed what seems to me to be a quirk, but wanted to see if this is correct behaviour, or perhaps my configuration. I am running a test install ov oVirt 3.3.2 in an all-in-one install. My test box only has one physical NIC, so I am using that for management/external network access, and I have create a dummy interface called dummy_0 to be used for the VMs. I created four networks, each assigned their own VLAN (I am wanted to simulate a real-world . I added the first network (VLAN001) to dummy_0 with no problem (I was able to save the configuration). The system created the dummy_0.1. When I tried to add another network (VLAN002) to dummy_0 and save it, I got the following error: --- START --- Error while executing action: local_host: Cannot setup Networks. The following Network Interfaces were specified more than once: dummy_0.1. --- END --- I found that in the Setup Host Network if I dragged VLAN001 off dummy_0 to the right under Required, and left VLAN002 on dummy_0, I could save it, and VLAN001 appeared to remain active on the host. Indeed, when I went back into Setup Host Network, both VLAN001 and VLAN002 were showing up on dummy_0. However, if I highlight VLAN002 under Networks and click on the Hosts tab, the Network Interface is showing a red down arrow, indicating it is not up. The Network Interface for VLAN001 is a green up arrow. I have refreshed several times and at this point in time, have left it for almost thirty minutes, but it remains as a red down arrow. The same is true for the other two networks I tried adding: I was able to add them as above, but they are also showing a red down arrow. My questions: 1.) Is doing what I had to do to add additional networks to an interface normal, or is it a quirk of using a dummy interface? 2.) Any ideas why my additional networks are showing a red down arrow? Again, maybe a quirk of using a dummy interface? It's a quirk of oVirt at the moment :) The interface state as shown in the GUI currently has very little to do with whether there's connectivity on a network. There should be an open RFE for connectivity indicators, though I can't seem to find it at the moment. What it SHOULD tell you is whether a link is up or down on the host (administrative state), but according to this bug it doesn't even do that (will be fixed soon): https://bugzilla.redhat.com/show_bug.cgi?id=1038741 I am going to leave it overnight and see what happens (maybe some background process needs to run??), but if that does not work, I am sure I can scrounge up another NIC in the next couple of days and install it into my test server to see if it does the same thing. Thanks, in advance. -Alan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Error: The following Network Interfaces were specified more than once:
Quoting Assaf Muller amul...@redhat.com:
Please run:
vdsClient -s 0 getVdsCaps
Here you go:
--- START ---
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:63b5586465eb'}]}
ISCSIInitiatorName = 'iqn.1994-05.com.redhat:63b5586465eb'
bondings = {'bond0': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond1': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond2': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond3': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond4': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []}}
bridges = {'VLAN001': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN001',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.1'],
'stp': 'off'},
'VLAN002': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN002',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.2'],
'stp': 'off'},
'VLAN009': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN009',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.9'],
'stp': 'off'},
'VLAN010': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN010',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.10'],
'stp': 'off'},
'ovirtmgmt': {'addr': '10.20.37.104',
'cfg': {'BOOTPROTO': 'dhcp',
'DEFROUTE': 'yes',
'DELAY': '0',
'DEVICE':
Re: [Users] Error: The following Network Interfaces were specified more than once:
Quoting Lior Vernia lver...@redhat.com: It's a quirk of oVirt at the moment :) The interface state as shown in the GUI currently has very little to do with whether there's connectivity on a network. There should be an open RFE for connectivity OK, so at this point it is a cosmetic issue as opposed to a functional one? -Alan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Error: The following Network Interfaces were specified more than once:
Thanks Alan, that confirms that it was the issue I had in mind.
This bug is fixed in oVirt 3.4, which has a first beta release out.
Assaf Muller, Cloud Networking Engineer
Red Hat
- Original Message -
From: Alan Murrell li...@murrell.ca
To: users@ovirt.org
Sent: Wednesday, January 29, 2014 4:58:59 PM
Subject: Re: [Users] Error: The following Network Interfaces were
specified more than once:
Quoting Assaf Muller amul...@redhat.com:
Please run:
vdsClient -s 0 getVdsCaps
Here you go:
--- START ---
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:63b5586465eb'}]}
ISCSIInitiatorName = 'iqn.1994-05.com.redhat:63b5586465eb'
bondings = {'bond0': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond1': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond2': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond3': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []},
'bond4': {'addr': '',
'cfg': {},
'hwaddr': '00:00:00:00:00:00',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []}}
bridges = {'VLAN001': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN001',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.1'],
'stp': 'off'},
'VLAN002': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN002',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.2'],
'stp': 'off'},
'VLAN009': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN009',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs': ['fe80::2ccd:eff:fee5:6a65/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': ['dummy_0.9'],
'stp': 'off'},
'VLAN010': {'addr': '',
'cfg': {'DEFROUTE': 'no',
'DELAY': '0',
'DEVICE': 'VLAN010',
'NM_CONTROLLED': 'no',
'ONBOOT': 'yes',
'STP': 'no',
'TYPE': 'Bridge'},
'gateway': '0.0.0.0',
'ipv6addrs
