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,
- 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
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
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 =
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
, 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
6 matches
Mail list logo