Update to 22.1.5 removes all Unbound Aliases!

[5SpeedFun]

I wonder if the unbound alias dissapearance is the same as what I saw when I was testing a dev version back in feb.  Same issue?  Or just the same symptoms?

https://forum.opnsense.org/index.php?topic=26700.msg132051#msg132051

[franco]

Well, same component, different issue.


Cheers,
Franco

[mnaim]

Hi, I was on 22.1.5 and aliases were visible. After upgrade to 22.1.6 (and restart) they are gone. Still present in XML in unboundplus section and DNS resolution is ok.

[franco]

Check configuration history, but in general this doesn't match how the migration works... it works from 22.1.4 to 22.1.5 and 22.1.6 changes nothing about that fact.


Cheers,
Franco

[mnaim]

2.1.6 - downloaded running config and records are there
Aliases page - No results found!

I think it is purely GUI bug.
If I call this API /api/unbound/settings/searchHostAlias/ aliases are returned ok in json.
But when they are called by page, response is {"rows":[],"rowCount":0,"total":0,"current":1}
This is what I see in browser debug-network. Private mode did not helped.

[mnaim]

Maybe I found error.

When I compare request to /api/unbound/settings/searchHostOverride/ and subsequent /api/unbound/settings/searchHostAlias/ only difference is that first has this request payload current=1&rowCount=7&searchPhrase= and second current=1&rowCount=7&searchPhrase=&host=__not_found__

If I remove &host=__not_found__ and run request, data are returned back successfully.

[mnaim]

Ah, I think I found new logic - but dont know if it is logic or bug

I have to select Host on top to see alias in bottom?
That's terribly counter intuitive - when I want to find alias, I need to click on 50 hosts if some of them have aliases to be displayed.
When nothing is selected on top, all aliases should be displayed.

Even when selecting, there is something wrong. When selected, 2 requests are generated in browser, first is immediately canceled and second pass.

[franco]

Can you try a different browser to see if it's not a cache issue?


Cheers,
Franco

[mnaim]

Tried MS Edge and Firefox - same.
Updated 5 Opnsense firewalls and all behave same :/

[mnaim]

When page is loaded
1) first request with host=__not_found__ is send to server
2) second request with host=GUID of first host is selected in hosts table by default

That's why it is filtering aliases in alias table and all aliases cant be displayed.

[katamadone [CH]]

https://forum.opnsense.org/index.php?topic=28161.0
https://forum.opnsense.org/index.php?topic=27861.0

should it be fixed with 22.1.6?

or is it maybe a problem that the users didn't realize and have to migrate like stated in https://github.com/opnsense/core/commit/ff11cde38e8 ?