On Tue, Jun 5, 2018 at 4:37 PM, Simone Tiraboschi <stirabos(a)redhat.com>
wrote:
On Tue, Jun 5, 2018 at 2:22 PM, Mariusz Kozakowski <mariusz.kozakowski@
sallinggroup.com> wrote:
> On Tue, 2018-06-05 at 13:43 +0200, Simone Tiraboschi wrote:
>
> Can you please share your /var/log/vdsm/vdsm.log and
> /var/log/vdsm/supervdsm.log ?
>
>
> Yes, please find the attached.
>
> On a seccesful setup in the logs you should see something like
2018-06-05 10:51:53,451+0200 INFO (jsonrpc/7) [api.network] START
setupNetworks(networks={u'ovirtmgmt': {u'ipv6autoconf': True,
u'nic':
u'eth0', u'mtu': 1500, u'switch': u'legacy',
u'dhcpv6': False, u'STP':
u'no', u'bridged': u'true', u'defaultRoute': True,
u'bootproto': u'dhcp'}},
bondings={}, options={u'connectivityCheck': u'true',
u'connectivityTimeout': 120}) from=::ffff:192.168.122.37,49716,
flow_id=41ca4fc1 (api:46)
but it's completely missing on your logs.
Can you please attach also the whole engine.log and host-deploy logs?
I tried to deploy hosted-engine over vlan over a bond and everything worked
as expected but I also found a case where it fails: SetupNetworks is going
to fail if bond0.123 is correctly configured with an IPv4 address while the
untagged bond0 lacks IPv4 configuration.
Simply configuring a static IPv4 address from an unused subnet on the
untagged bond is a valid workaround.
I just opened
https://bugzilla.redhat.com/show_bug.cgi?id=1586280
>
> --
>
> Best regards/Pozdrawiam/MfG
>
> *Mariusz Kozakowski*
>
> Site Reliability Engineer
>
> Dansk Supermarked Group
> Baltic Business Park
> ul. 1 Maja 38-39
> 71-627 Szczecin
>
dansksupermarked.com
>