You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect to get an error-message that something is wrong with the ip-address or hostname, that there is no exception in the logs, and that the attempt is not logged as a 500 Sever error in the access log.
Environment (please complete the following information):
"docker compose up"
debian bullseye
Nav is latest master
The text was updated successfully, but these errors were encountered:
lunkwill42
changed the title
[BUG] Improperly caught exception/error handling when adding a new ip device
[BUG] Improperly caught exception/error handling when checking device connectivity from SeedDB
Nov 8, 2023
I changed the title, since this isn't actually a bug that comes from adding a device, but rather from check device connectivity with the chosen management profiles. You can still add the device without checking connectivity, and that should properly validate the IP address input.
Attempt to add an ip-device in seeddb with a hostname/ip-address that does not exist.
Also, by "ip-address that does not exist", I assume you mean "an invalid ip-address" ? If a valid address is entered, but no device has that ip address, the address could be said to not exist, but that will not crash the UI AFAIK, it will properly report that the device isn't responding.
Describe the bug
Attempt to add an ip-device in seeddb with a hostname/ip-address that does not exist.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to get an error-message that something is wrong with the ip-address or hostname, that there is no exception in the logs, and that the attempt is not logged as a 500 Sever error in the access log.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: