> 1)      Verify network got failed with message Expected VLAN (not
> received) untagged at the interface Eth1 of controller and compute nodes.
> In our set-up Eth1 is connected to the public network, which we disconnect
> from public network while doing deployment operation as FUEL itself works
> as DHCP server. We want know that is this a known issue in Fuel or from our
> side, as we followed this prerequisite before doing verify network
> operation.
 The fact of error is correct - no received traffic on eth1. But what is
expected behaviour from your point of view?

> 2)      Eth1 interface in the Fuel UI is showing as down even after
> connecting back cables into the nodes.
> Before doing openstack deployment  from Fuel node, we disconnected eth1
> from controller and compute nodes as it is connected to public network.
> Deployment was successful and then we connected back the Eth1 of all
> controller/compute nodes.  We are seeing an issue that eth1 displaying as
> down in FUEL UI, even though we connect back eth1 interface and we are able
> to ping to public network.
Probably we disabled interface information update, after node is deployed,
and imho we need to open bug for this issue
OpenStack-dev mailing list

Reply via email to