2:02 a.m.
I have installed a hosted engine setup on a single host. The host is
running CentOS 7 and the engine is Centos 6.6.
Prior to running through the engine deployment, I created the
ifcfg-ovirtmgmt file and set my primary network interface, "eno1", as
part of that bridge. I did this because when I have attempted
deployment in the past, the deployment ran into some problems creating
the 'ovirtmgmt' bridge. I do recall during the deployment script, the
output did indicate that it saw the 'ovirtmgmt' bridge was already
present. The deployment *seemed* to go OK.
Upon logging in to the admin portal, my host is not initialised; it has
a red "X". The error indicated that the "ovirtmgmt" bridge was not
assigned to an interface.
When I click on the host then "Network Interfaces", all my network
interfaces are showing red "down" arrows (which makes sense if the host
is not initialised). When I click on "Setup Network Interfaces", it
lists my physical interfaces on the left and on the right, under
"Unassigned Logical networks" is "ovirtmgmt".
I Assigned "ovirtmgmt" to interface "eno1", but when I click
"OK", I get
the following message:
--- START ---
Error while executing action:
hosted_engine_1:
* Network address must be specified when using static ip
--- END ---
I tried to edit "ovirtmgmt" and assign the static IP, but the same error
comes up.
Here are my files for 'ifcfg-eno1' and 'ifcfg-ovirtmgmt':
--- START ifcfg-ovirtmgmt ---
TYPE="Bridge"
BOOTPROTO="static"
DEVICE="ovirtmgmt"
ONBOOT="yes"
DELAY="0"
IPADDR="10.215.1.21"
NETMASK="255.255.255.0"
GATEWAY="10.215.1.1"
--- END ifcfg-ovirtmgmt ---
--- START ifcfg-eno1 ---
TYPE="Ethernet"
BOOTPROTO="none"
DEVICE="eno1"
ONBOOT="yes"
BRIDGE="ovirtmgmt"
--- END ifcfg-eno1 ---
Here is the output of 'brctl show':
--- START ---
bridge name bridge id STP enabled interfaces
;vdsmdummy; 8000.000000000000 no
ovirtmgmt 8000.fc4dd4f2e238 no eno1
vnet0
--- END ---
It appears that the bridge exists, but the system (VDSM?) is not
recognising it nor able to create it.
Any ideas what the issue is? If you need a look at something else,
please let me know. I may not be able to post it until later (my server
is remote to me until Wednesday so I won;t have immediate access), but I
will post whatever else you need to have a look at.
Thanks! :-)
-Alan
2:22 a.m.
On Tue, Jul 21, 2015 at 9:02 AM, Alan Murrell <lists(a)murrell.ca> wrote:
I have installed a hosted engine setup on a single host. The host
is
running CentOS 7 and the engine is Centos 6.6.
Prior to running through the engine deployment, I created the
ifcfg-ovirtmgmt file and set my primary network interface, "eno1", as part
of that bridge. I did this because when I have attempted deployment in
the past, the deployment ran into some problems creating the 'ovirtmgmt'
bridge.
If at all possible, please try that again. If there are still unsolved
bugs, we'd
like to know.
I do recall during the deployment script, the output did indicate
that it saw the 'ovirtmgmt' bridge was already present. The deployment
*seemed* to go OK.
You might want to check/post also the output of 'vdsClient -s 0 getVdsCaps',
especially 'bridges', 'networks' and 'nics' there.
Upon logging in to the admin portal, my host is not initialised; it has a
red "X". The error indicated that the "ovirtmgmt" bridge was not
assigned
to an interface.
When I click on the host then "Network Interfaces", all my network
interfaces are showing red "down" arrows (which makes sense if the host is
not initialised). When I click on "Setup Network Interfaces", it lists my
physical interfaces on the left and on the right, under "Unassigned Logical
networks" is "ovirtmgmt".
I Assigned "ovirtmgmt" to interface "eno1", but when I click
"OK", I get the
following message:
--- START ---
Error while executing action:
hosted_engine_1:
* Network address must be specified when using static ip
--- END ---
I tried to edit "ovirtmgmt" and assign the static IP, but the same error
comes up.
Here are my files for 'ifcfg-eno1' and 'ifcfg-ovirtmgmt':
--- START ifcfg-ovirtmgmt ---
TYPE="Bridge"
BOOTPROTO="static"
DEVICE="ovirtmgmt"
ONBOOT="yes"
DELAY="0"
IPADDR="10.215.1.21"
NETMASK="255.255.255.0"
GATEWAY="10.215.1.1"
--- END ifcfg-ovirtmgmt ---
--- START ifcfg-eno1 ---
TYPE="Ethernet"
BOOTPROTO="none"
DEVICE="eno1"
ONBOOT="yes"
BRIDGE="ovirtmgmt"
--- END ifcfg-eno1 ---
I don't have currently a setup with static addresses, so it's just a guess:
Perhaps you need 'NETWORK='?
Here is the output of 'brctl show':
--- START ---
bridge name bridge id STP enabled interfaces
;vdsmdummy; 8000.000000000000 no
ovirtmgmt 8000.fc4dd4f2e238 no eno1
vnet0
--- END ---
It appears that the bridge exists, but the system (VDSM?) is not recognising
it nor able to create it.
Any ideas what the issue is? If you need a look at something else, please
let me know. I may not be able to post it until later (my server is remote
to me until Wednesday so I won;t have immediate access), but I will post
whatever else you need to have a look at.
Well, you can check/post also vdsm and engine logs.
Adding Dan.
Best,
--
Didi
5:27 a.m.
On Tue, Jul 21, 2015 at 09:22:02AM +0300, Yedidyah Bar David wrote:
On Tue, Jul 21, 2015 at 9:02 AM, Alan Murrell
<lists(a)murrell.ca> wrote:
> I have installed a hosted engine setup on a single host. The host is
> running CentOS 7 and the engine is Centos 6.6.
>
> Prior to running through the engine deployment, I created the
> ifcfg-ovirtmgmt file and set my primary network interface, "eno1", as
part
> of that bridge. I did this because when I have attempted deployment in
> the past, the deployment ran into some problems creating the 'ovirtmgmt'
> bridge.
If at all possible, please try that again. If there are still unsolved
bugs, we'd
like to know.
> I do recall during the deployment script, the output did indicate
> that it saw the 'ovirtmgmt' bridge was already present. The deployment
> *seemed* to go OK.
You might want to check/post also the output of 'vdsClient -s 0 getVdsCaps',
especially 'bridges', 'networks' and 'nics' there.
virsh -r dumpxml vdsm-ovirtmgmt
may be interesting, too. If you go native and define ovirtmgmt bridge on
your own, you should also define that network. Skipping network
definition might have worked in the past, but it would certainly not
work on 3.6.
>
> Upon logging in to the admin portal, my host is not initialised; it has a
> red "X". The error indicated that the "ovirtmgmt" bridge was
not assigned
> to an interface.
>
> When I click on the host then "Network Interfaces", all my network
> interfaces are showing red "down" arrows (which makes sense if the host
is
> not initialised). When I click on "Setup Network Interfaces", it lists
my
> physical interfaces on the left and on the right, under "Unassigned Logical
> networks" is "ovirtmgmt".
>
> I Assigned "ovirtmgmt" to interface "eno1", but when I click
"OK", I get the
> following message:
>
> --- START ---
> Error while executing action:
>
> hosted_engine_1:
> * Network address must be specified when using static ip
> --- END ---
>
> I tried to edit "ovirtmgmt" and assign the static IP, but the same error
> comes up.
>
> Here are my files for 'ifcfg-eno1' and 'ifcfg-ovirtmgmt':
>
> --- START ifcfg-ovirtmgmt ---
> TYPE="Bridge"
> BOOTPROTO="static"
> DEVICE="ovirtmgmt"
> ONBOOT="yes"
> DELAY="0"
> IPADDR="10.215.1.21"
> NETMASK="255.255.255.0"
> GATEWAY="10.215.1.1"
> --- END ifcfg-ovirtmgmt ---
>
> --- START ifcfg-eno1 ---
> TYPE="Ethernet"
> BOOTPROTO="none"
> DEVICE="eno1"
> ONBOOT="yes"
> BRIDGE="ovirtmgmt"
> --- END ifcfg-eno1 ---
I don't have currently a setup with static addresses, so it's just a guess:
Perhaps you need 'NETWORK='?
>
> Here is the output of 'brctl show':
>
> --- START ---
> bridge name bridge id STP enabled interfaces
> ;vdsmdummy; 8000.000000000000 no
> ovirtmgmt 8000.fc4dd4f2e238 no eno1
> vnet0
> --- END ---
>
> It appears that the bridge exists, but the system (VDSM?) is not recognising
> it nor able to create it.
>
> Any ideas what the issue is? If you need a look at something else, please
> let me know. I may not be able to post it until later (my server is remote
> to me until Wednesday so I won;t have immediate access), but I will post
> whatever else you need to have a look at.
Well, you can check/post also vdsm and engine logs.
Adding Dan.
Best,
--
Didi
7:34 p.m.
Hi Dan,
Quoting "Dan Kenigsberg" <danken(a)redhat.com>:
virsh -r dumpxml vdsm-ovirtmgmt
I will see if I can get you that output a little later, along with the
vdsClient output suggested by Yedidyah.
your own, you should also define that network. Skipping network
definition might have worked in the past, but it would certainly not
When you refer to defining the "network definition", are you referring
to a "NETWORK=" line in my ifcfg-ovirtmgmt file (which I think was
referred to by Yedidyah)?
If necessary, I can also blow away my current install and try the
deployment again without defining the bridge first, if for no other
reason than if it still fails to do so, it is a bug that that you will
be aware of.
Regards,
Alan
2:23 a.m.
On Wed, Jul 22, 2015 at 2:34 AM, Alan Murrell <lists(a)murrell.ca> wrote:
Hi Dan,
Quoting "Dan Kenigsberg" <danken(a)redhat.com>:
>
> virsh -r dumpxml vdsm-ovirtmgmt
I will see if I can get you that output a little later, along with the
vdsClient output suggested by Yedidyah.
> your own, you should also define that network. Skipping network
> definition might have worked in the past, but it would certainly not
When you refer to defining the "network definition", are you referring to a
"NETWORK=" line in my ifcfg-ovirtmgmt file (which I think was referred to by
Yedidyah)?
Dan refers to the below:
If necessary, I can also blow away my current install and try the deployment
again without defining the bridge first, if for no other reason than if it
still fails to do so, it is a bug that that you will be aware of.
Yes, please do. This will be mandatory in 3.6.
Thanks, and please report back with any issue (or success :-) ).
Best,
--
Didi
7 a.m.
On Wed, Jul 22, 2015 at 09:23:46AM +0300, Yedidyah Bar David wrote:
On Wed, Jul 22, 2015 at 2:34 AM, Alan Murrell
<lists(a)murrell.ca> wrote:
> Hi Dan,
>
> Quoting "Dan Kenigsberg" <danken(a)redhat.com>:
>>
>> virsh -r dumpxml vdsm-ovirtmgmt
>
>
> I will see if I can get you that output a little later, along with the
> vdsClient output suggested by Yedidyah.
>
>> your own, you should also define that network. Skipping network
>> definition might have worked in the past, but it would certainly not
>
>
> When you refer to defining the "network definition", are you referring to
a
> "NETWORK=" line in my ifcfg-ovirtmgmt file (which I think was referred to
by
> Yedidyah)?
Dan refers to the below:
Actually, I was referring to placing a file (say /tmp/1.xml) with
<network>
<name>vdsm-ovirtmgmt</name>
<uuid>f661da6b-6dea-8c4d-af7f-c0c9111ea10e</uuid>
<forward mode='bridge'/>
<bridge name='ovirtmgmt'/>
</network>
and defining it in libvirt with
virsh net-define /tmp/1.xml
virsh net-start vdsm-ovirtmgmt
but not that I do not endorse it; the following is what should be followed:
>
> If necessary, I can also blow away my current install and try the deployment
> again without defining the bridge first, if for no other reason than if it
> still fails to do so, it is a bug that that you will be aware of.
Yes, please do. This will be mandatory in 3.6.
Thanks, and please report back with any issue (or success :-) ).
Best,
--
Didi
1:23 a.m.
OK, so I blew away my hosted engine and removed my "ovirmgmt" interface
(returning it back to the original "eno1" and on my host ran through the
deployment again. Everything wen through fine.
Thanks! :-)
-Alan
2:19 a.m.
On Thu, Jul 23, 2015 at 8:23 AM, Alan Murrell <lists(a)murrell.ca> wrote:
OK, so I blew away my hosted engine and removed my
"ovirmgmt" interface
(returning it back to the original "eno1" and on my host ran through the
deployment again. Everything wen through fine.
Thanks! :-)
Thanks for the report!
Best,
--
Didi
3211
days inactive
3213
days old
7 comments
3 participants
participants (3)
-
Alan Murrell -
Dan Kenigsberg -
Yedidyah Bar David