web admin: high-availability setting is not display correctly when editing an interface

[nqb]

Describe the bug
When you edit an interface with type=high-availability, web admin doesn't display correct setting.

To Reproduce
Steps to reproduce the behavior:

1. Configure your management interface as high-availability
2. Save
3. Leave current view
   

=> high-availability appears as an additional daemon which is wrong

4. Click on your interface

=> high-availability appears as an additional daemon but not as a setting enabled.

Expected behavior
high-availability should:

• not appear as an additional daemon
• appear as enabled when that is the case

Additional context
pf.conf after I enabled high-availability on my interface:

[interface eth1]
ip=172.17.17.10
type=management,portal,high-availability
mask=255.255.255.0

When I try to display my interface (step 4), I see following return from API:

    "item": {
      "additional_listening_daemons": [
        "portal",
        "high-availability"
      ],
      "address": "172.17.17.10/24",
[..]
      "high_availability": 1,
[..]

[nqb]

Additional note: on a setup with no portal daemon listening on management interface, high-availability appears as disabled and doesn't appear as additional daemon.

[nqb]

@jrouzierinverse, I opened #5964 and push a fix to see if frontend can't display correctly value return by frontend.

Could you check on your side why high-availability appears as additional daemon and push to fix/5963 ?

Thanks

[rcmcdonald91]

#5680 I reported this back in July.

[nqb]

Thanks @theonemcdonald

[nqb]

Fix pushed to maintenance.