network connectivity checks fail on repo availability from public network

[Robert Duncan]

This bug looks like this one (fixed in 8.0)
https://bugs.launchpad.net/bugs/1535765

steps to reporduce
1. Fuel 9.0 iso
2. Add nodes
3. configure network parameters
4. configure interfaces
5. run network connectivity test

Expected results
pass

Actual Result - cannot access repos using the public interface
the network check drops out at this point and fails, bootstrap image has not brought up the hosts interfaces
only PXE interface is up

these are Dell C6145, R630 R730XD - same result bootstrap only brings up PXE interface.

workaround - manually bring up the interfaces.

env:
Fuel 9.0, Mitaka on Ubuntu+UCA
Neutron with tunneling segmentation

[Maksim Malchuk (mmalchuk)]

by default public interfaces configured during the deploy only.
bootstrap nodes uses only admin interface and default routing configured through the master node by default.
the master node should have internet access or you can configure default router for bootstrap nodes in the fuelmnu.

[Robert Duncan (rduncan-t)]

before deployment, on the connectivity check:
Repository connectivity check from the Fuel Slave nodes through the public & admin (PXE) networks.

always fails since public interfaces are not up.

[Maksim Malchuk (mmalchuk)]

please provide the diagnostic snapshot

[Robert Duncan (rduncan-t)]

It's 230MB - where to upload?

[Robert Duncan (rduncan-t)]

https://drive.google.com/file/d/0B5kz9lnnQlGMbnZDWEFKcVp4MTg/view?usp=sharing

[Oleksiy Molchanov (omolchanov)]

During connectivity check we need only PXE (admin) interface to be UP. Please check whether you have access to internet via admin network. Marking as Incomplete.

[Robert Duncan (rduncan-t)]

The Fuel UI says public & admin - also the connectivity check keeps failing unless the public interface are brought up - if the public and admin networks are assigned to the one nic then the test is passed

From the Fuel 9.0 UI:
Network verification checks the following:
1. L2 connectivity checks between nodes in the environment.
2. DHCP discover check on all nodes.
3. Repository connectivity check from the Fuel Master node.
4. Repository connectivity check from the Fuel Slave nodes through the public & admin (PXE) networks.

&&

Public network assignment

Assign public network to all nodes
When disabled, public network will be assigned to controllers only

For me the connectivity check kept failing and what 'fixed' the issue was bringing up the public interfaces, I suppose if the public and admin networks are assigned to one nic you won't see get the error

[Vladimir Kozhukalov (kozhukalov)]

Please be informed that both admin and public networks are untagged (not vlan interfaces) and they can not be assigned to the same interface. So, at least two physical interfaces are needed on slave nodes. One for admin network and another for public network (other networks like management, storage, etc. could be assigned on vlan interfaces). Fuel network manager component automatically assigns public and admin networks on different interfaces.

There are two types of repository checks from slave nodes
1) via master node (admin network)
2) via public gateway (public network)

When 1), there won't be any additional configuration on slave nodes. It is assumed Fuel master node is used as a gateway. By default it is 10.20.0.2 (172.25.10.2 for this particular case).

When 2), public interface (which is in down mode by default when a node in bootstrap) is configured TEMPORARILY (public ip is assigned and public gateway is configured as default). It is important that this public gateway which is 172.16.0.1 by default (193.1.202.1 for this particular case) MUST be working (it is not on the master node).

I attached a small sketch to the bug to exaplain all this stuff, but if you need details please refer to http://docs.openstack.org/developer/fuel-docs/

[Robert Duncan (rduncan-t)]

Thanks Vladimir, this is how I expected the test was being performed - the default public interface in my case is a virtual interface on a firewall router, the fuel slave nodes have separate interfaces for all networks and no vlan tags. (all of these networks terminate at the firewall router) additionally the public network is assigned to an interface on all fuel slave nodes, so I would assume that all fuel slave nodes need to have their public interfaces up in bootstrap mode to pass the connectivity check. so for example, with one fuel master and 10 fuel slaves the connectivity test would check 22 network cards have access to fuel repositories.

[Vladimir Kozhukalov (kozhukalov)]

When running connectivity check fuel temporarily brings necessary interfaces up and configures them. By default only admin interface is up on bootstrap nodes when there is no any running network check test. Once a test is done, unneeded interfaces go down.