2:43 a.m.
Hi,
when running "hosted-engine --deploy" on a fresh CentOS 7.4 with pre-built
network configuration (and ovirtmgmt bridge), the following error occurs:
2017-11-27 19:08:12 DEBUG otopi.context context._executeMethod:142 method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py",
line 295, in _get_hostname_from_bridge_if
raise RuntimeError(_('Cannot acquire bridge address'))
RuntimeError: Cannot acquire bridge address
While checking the source of bridge.py line 295 the root cause is interesting:
Running "vdsClient -s $HOSTNAME getVdsCapabilities" works perfectly, all NICs
and bridges are returned, but only "networks" is returned as empty list: {}.
Clearly looks like a bug. How can I resolve this issue?
ovirt-hosted-engine-setup-2.1.4-1.el7.centos.noarch
vdsm-4.19.40-1.el7.centos.x86_64
Regards
- Frank
11:04 a.m.
On Tue, Nov 28, 2017 at 1:43 AM, Frank Wall <fw(a)moov.de> wrote:
Hi,
when running "hosted-engine --deploy" on a fresh CentOS 7.4 with pre-built
network configuration (and ovirtmgmt bridge), the following error occurs:
Hi Frank,
what happened to you is exactly https://bugzilla.redhat.com/1317125 which
has been closed as wontfix.
The point is that if you manually/directly create a bridge outside vdsm,
this one will not be associated with any logical network know by vdsm (as
you pointed out the networks field in getVdsCapabilities is empty) and so
we cannot match it.
In general we simply recommend to configure bonds and vlans as needed but
let hosted-engine-setup create a management bridge for you via vdsm over
the selected interface (it could be also a bond with a vlan tag).
If you still want to directly create the management bridge by yourself in
advance, but honestly I cannot understand why, you have to properly do it
with vdsm setup host network commands.
2017-11-27 19:08:12 DEBUG otopi.context context._executeMethod:142 method
exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
File "/usr/share/ovirt-hosted-engine-setup/scripts/../
plugins/gr-he-common/network/bridge.py", line 295, in
_get_hostname_from_bridge_if
raise RuntimeError(_('Cannot acquire bridge address'))
RuntimeError: Cannot acquire bridge address
While checking the source of bridge.py line 295 the root cause is
interesting:
Running "vdsClient -s $HOSTNAME getVdsCapabilities" works perfectly, all
NICs
and bridges are returned, but only "networks" is returned as empty list:
{}.
Clearly looks like a bug. How can I resolve this issue?
ovirt-hosted-engine-setup-2.1.4-1.el7.centos.noarch
vdsm-4.19.40-1.el7.centos.x86_64
Regards
- Frank
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:46 a.m.
Hi Simone,
thanks for your quick reply, much appreciated!
On Tue, Nov 28, 2017 at 10:04:10AM +0100, Simone Tiraboschi wrote:
what happened to you is exactly https://bugzilla.redhat.com/1317125
which
has been closed as wontfix.
I've seen this bugzilla issue, but TBH I was a bit baffled. Back in the days
of oVirt 3.x it was *mandatory* to setup the bridge manually, now it's
unsupported. :D
I remember setting up a 4.0.x environment earlier this year and did not
experience this issue. And I couldn't find any information as to which release
introduced this (breaking) change.
Several places still talk about manually creating bridges, maybe it would
be a good idea to remove this dated documentation or add a hint that this
does not apply to the current release:
https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
(There might be more pages, I haven't done an extensive search.)
Regards
- Frank
7:15 p.m.
On Tue, Nov 28, 2017 at 10:46 AM, Frank Wall <fw(a)moov.de> wrote:
Hi Simone,
thanks for your quick reply, much appreciated!
On Tue, Nov 28, 2017 at 10:04:10AM +0100, Simone Tiraboschi wrote:
> what happened to you is exactly https://bugzilla.redhat.com/1317125
which
> has been closed as wontfix.
I've seen this bugzilla issue, but TBH I was a bit baffled. Back in the
days
of oVirt 3.x it was *mandatory* to setup the bridge manually, now it's
unsupported. :D
Technically hosted-engine-setup was already using vdsm to create the
management network in its 1.0 release
https://gerrit.ovirt.org/#/c/16716/
so I don't think we ever required to manually do it just for that purpose
or at least not on common configurations.
I remember setting up a 4.0.x environment earlier this year and did not
experience this issue. And I couldn't find any information as to which
release
introduced this (breaking) change.
Several places still talk about manually creating bridges, maybe it would
be a good idea to remove this dated documentation or add a hint that this
does not apply to the current release:
https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
(There might be more pages, I haven't done an extensive search.)
I'm absolutely with you on this: by the way that page still recommends to
disable NetwokrManager which instead is not an issue today.
Regards
- Frank
2349
days inactive
2349
days old
3 comments
2 participants
participants (2)
-
Frank Wall -
Simone Tiraboschi