Dashboard link status always OK?

(Charlie Lehardy) #1

I’ve configured a blue network but haven’t yet plugged anything into it. When I go to Config/Network and edit the blue lan, it shows that the link status is “down,” which is correct. But on the dashboard under interfaces, the blue network link status shows as OK. Perhaps this has a different meaning, but it would be helpful if the dashboard reflected at a glance whether a particular network was up or down. Or maybe I have something misconfigured? Thanks.

(Filippo Carletti) #2

I just checked on of my systems and I can observe a similar behaviour. I think it’s related to the hardware model of the boards.
In my case I have two unused ethernet boards and the dashboard shows different data for them:
eth1: two lines, MAC and link:-
eth3: four lines, MAC, link OK (100 Mb/s), IP -/- and type -

I’ll ask @giacomo to check the code. :smile:

(Giacomo Sanchietti) #3

I didn’t check the code, but I bet it’s a bug.
We have plans to rewrite the dashboard using the same code from the network module.

I will keep u posted :smile:

(Charlie Lehardy) #4

Thanks for looking into this.

(Giacomo Sanchietti) #5

The fix is now on QA: http://dev.nethserver.org/issues/3096

(Alessio Fattorini) #6

@AZChas QA is coming up do you want to lend a hand?

Building Quality Team
(Charlie Lehardy) #7

I’d love to. Count me in.

(Alessio Fattorini) #8
  • prepare a NethServer fresh install
  • verify bug presence
  • update with
    Yum --enablerepo=nethserver-testing update nethserver-base
  • follow test case described into the bug
  • if success mark as Verify otherwise mark as failed and explain why, for example pasting error messages

Building Quality Team
Building Quality Team
(Charlie Lehardy) #9

I did a fresh install and verified that the bug was present. Downloaded and installed the patch, rebooted, and the dashboard status indicators now function correctly.

(Alessio Fattorini) #10

That’s great! Your first QA :+1: :+1:

(Giacomo Sanchietti) #11

The bug is now set to VERIFIED: http://dev.nethserver.org/issues/3096