Mirantis Fuel 9.0 Dose Not shows Network Up or down

[Khadeer]

Hi Every One

There is a issue with Mirantis Fuel 9.0
If a Server Hardware has Two NIC Cards In Fuel 9.0 the Admin Network which is fuel network show Green and Up, Where the the other Network which Openstack Network Show Down
NAMEenp4s0f0
MAC00:30:48:c2:12:7e
STATEup
IP10.18.203.29
NETMASK255.255.255.0
CURRENT SPEED1.0 Gbps
MAX SPEED1.0 Gbps
DRIVERe1000e
BUS INFO0000:04:00.0
PXETrue
NAMEenp4s0f1
MAC00:30:48:c2:12:7f
STATEdown
CURRENT SPEED1.0 Gbps
MAX SPEED1.0 Gbps
DRIVERe1000e
BUS INFO0000:04:00.1
PXEFalse

Where when I Test the network it will pass It dose not give any error.
My question is Why dose the other network shows down and why the network check getting successful.

Another Bug

In the same above scenario If the server is having 10 GIG NIC Card i.e EX:"10 GIG Mellanox card" Then the Network check is getting failed.

All the above servers and the network configuration are fully check in Fuel 7, 8.0 where it is working perfectly.

This will vary helpful if resolved

[Khadeer (kmdkhadeer78)]

Hi Dmitry

There still same issue any updates on this it will vary helpful.

[Andres Toomsalu (andres-active)]

Same problem on Mitaka 9.1. Dell R630 has integrated 2x10Gbit + 2x1Gbit and additional 2x10Gbit card.

PCIe Slot 3 Intel(R) 10GbE 2P X520 Adapter 8x or x8
Embedded 82599ES 10-Gigabit SFI/SFP+ Network Connection N/A
Embedded 82599ES 10-Gigabit SFI/SFP+ Network Connection N/A
Embedded Intel(R) x520 DP 1Gb BT + DP 10Gb SFP+ Rack NDC N/A
Embedded Intel(R) x520 DP 1Gb BT + DP 10Gb SFP+ Rack NDC

Only the first interface (eno1) is getting link with bootstrap image, for the others ethtool shows "Link detected: no".

However dmesg shows that each port have had a link on boot (but disabled at later stage perhaps?):

root@node-1:~# dmesg | grep 'ixgbe'
[ 4.857336] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
[ 10.476729] ixgbe 0000:01:00.0: registered PHC device on eno1
[ 10.642335] ixgbe 0000:01:00.0 eno1: detected SFP+: 4
[ 10.781958] ixgbe 0000:01:00.0 eno1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[149314.079278] ixgbe 0000:01:00.1: registered PHC device on eno2
[149314.246412] ixgbe 0000:01:00.1 eno2: detected SFP+: 3
[149314.386132] ixgbe 0000:01:00.1 eno2: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[149315.398571] ixgbe 0000:04:00.0: registered PHC device on enp4s0f0
[149315.565169] ixgbe 0000:04:00.0 enp4s0f0: detected SFP+: 3
[149315.704829] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[149316.721207] ixgbe 0000:04:00.1: registered PHC device on enp4s0f1
[149316.887883] ixgbe 0000:04:00.1 enp4s0f1: detected SFP+: 4
[149317.127423] ixgbe 0000:04:00.1 enp4s0f1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[149324.186380] ixgbe 0000:01:00.1: removed PHC on eno2
[149324.270194] ixgbe 0000:04:00.0: removed PHC on enp4s0f0
[149324.353860] ixgbe 0000:04:00.1: removed PHC on enp4s0f1
[150061.264521] ixgbe 0000:01:00.1: registered PHC device on eno2
[150061.431909] ixgbe 0000:01:00.1 eno2: detected SFP+: 3
[150061.571630] ixgbe 0000:01:00.1 eno2: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[150062.582976] ixgbe 0000:04:00.0: registered PHC device on enp4s0f0
[150062.750655] ixgbe 0000:04:00.0 enp4s0f0: detected SFP+: 3
[150062.890328] ixgbe 0000:04:00.0 enp4s0f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[150063.902359] ixgbe 0000:04:00.1: registered PHC device on enp4s0f1
[150064.069384] ixgbe 0000:04:00.1 enp4s0f1: detected SFP+: 4
[150064.209024] ixgbe 0000:04:00.1 enp4s0f1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[150071.383888] ixgbe 0000:01:00.1: removed PHC on eno2
[150071.468088] ixgbe 0000:04:00.0: removed PHC on enp4s0f0
[150071.551778] ixgbe 0000:04:00.1: removed PHC on enp4s0f1

Settings for eno2:
 Supported ports: [ FIBRE ]
 Supported link modes: 10000baseT/Full
 Supported pause frame use: No
 Supports auto-negotiation: No
 Advertised link modes: 10000baseT/Full
 Advertised pause frame use: No
 Advertised auto-negotiation: No
 Speed: 10000Mb/s
 Duplex: Full
 Port: Direct Attach Copper
 PHYAD: 0
 Transceiver: external
 Auto-negotiation: off
 Supports Wake-on: umbg
 Wake-on: g
 Current message level: 0x00000007 (7)
          drv probe link
 Link detected: no

Now when I add interface profile under /etc/network/interfaces.d - like:
--- EXAMPLE ---
root@bootstrap:~# ca...

[Vladimir Kuklin (vkuklin)]

This is expected behaviour - we have only admin interface on the bootstrapped nodes set to UP state. Then we turn them on and off during network verification only when it is needed.

[Andres Toomsalu (andres-active)]

Well - network verification fails if interfaces are down (network verification DOES NOT bring them up by itself). Thats the problem.

[Khadeer (kmdkhadeer78)]

I have worked on previous version for Fuel like Fuel 6.0,6.1,7,8

In all the above mentioned fuel version the network status use to show "IF
UP " then show green "IF Down" if show grade out.
In Fuel 9 and 9.1 the only Admin Network NIC card shows UP and Green.
Where as other Nic card which are connect even Fuel show them Down and
 grade out. But the as check even it down when i did network test is able
to pass. Hence the issue is with Fuel which is not able to detect other NIC
card status other then admin Network.

Regards
Mohammed Khadeer
Mob:[phone]

On Fri, Dec 16, 2016 at 6:01 PM, Vladimir Kuklin <email address hidden>
wrote:

> This is expected behaviour - we have only admin interface on the
> bootstrapped nodes set to UP state. Then we turn them on and off during
> network verification only when it is needed.
>
> ** Changed in: fuel
> Status: Confirmed => Invalid
>
> ** Changed in: fuel/mitaka
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1605420
>
> Title:
> Mirantis Fuel 9.0 Dose Not shows Network Up or down
>
> Status in Fuel for OpenStack:
> Invalid
> Status in Fuel for OpenStack mitaka series:
> Invalid
>
> Bug description:
> Hi Every One
>
> There is a issue with Mirantis Fuel 9.0
> If a Server Hardware has Two NIC Cards In Fuel 9.0 the Admin Network
> which is fuel network show Green and Up, Where the the other Network which
> Openstack Network Show Down
> NAMEenp4s0f0
> MAC00:30:48:c2:12:7e
> STATEup
> IP10.18.203.29
> NETMASK255.255.255.0
> CURRENT SPEED1.0 Gbps
> MAX SPEED1.0 Gbps
> DRIVERe1000e
> BUS INFO0000:04:00.0
> PXETrue
> NAMEenp4s0f1
> MAC00:30:48:c2:12:7f
> STATEdown
> CURRENT SPEED1.0 Gbps
> MAX SPEED1.0 Gbps
> DRIVERe1000e
> BUS INFO0000:04:00.1
> PXEFalse
>
> Where when I Test the network it will pass It dose not give any error.
> My question is Why dose the other network shows down and why the network
> check getting successful.
>
> Another Bug
>
> In the same above scenario If the server is having 10 GIG NIC Card i.e
> EX:"10 GIG Mellanox card" Then the Network check is getting failed.
>
> All the above servers and the network configuration are fully check in
> Fuel 7, 8.0 where it is working perfectly.
>
> This will vary helpful if resolved
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1605420/+subscriptions
>