Hostname Database regression in SCALE 22.02-RC.2
Description
Problem/Justification
Impact
Activity

Jon C. ThomasonJanuary 24, 2022 at 6:24 PMEdited
Thanks! PR #8128 LGTM.
FWIW I might have added user entries after the static system entries, lest they take precedence. But this will fix the regression as-is.
To answer your other questions:
I'd added my entries via GUI under Network, Global Configuration.
The error message was a Python traceback ending in a sockets errno, as follows.
I myself knew to hunt this down as a hostname resolution problem. But since I hadn't been trying out new settings/credentials, there was no implicit context for why my established replications had stopped.
If I had been trying to set up a new replication, IMO a novice user might appreciate your catching this exception to report something like:
Error: Hostname 'remoteserver' not found. Check your SSH Connections, under Backup Credentials.
Or simply:
Error: SSH host 'remoteserver' could not be reached.
Instead, unfortunately, they will have seen this:
[EFAULT] [Errno -2] Name or service not known.

CalebJanuary 11, 2022 at 9:25 PM
What was the inscrutable error message?
How were you using the hostname database? Were you doing it manually via the CLI? Are you inserting entries via the webUI?

Jon C. ThomasonDecember 31, 2021 at 11:15 PM
Private debugs for two SCALE systems: each showing host entries in the middleware which are not reflected in /etc/hosts.

iX-TonyDecember 31, 2021 at 9:09 PM
Thank you for the report, . Can you please attach a debug file to the "Private Attachments" section of this ticket? To generate a debug file on TrueNAS SCALE, log in to the TrueNAS web interface, go to System Settings > Advanced, then click Save Debug and wait for the file to download to your local system.
Details
Assignee
CalebCalebReporter
Jon C. ThomasonJon C. ThomasonLabels
Impact
MediumTime remaining
0mComponents
Fix versions
Priority
Low
Details
Details
Assignee

Reporter

The /etc/hosts file in SCALE 22.02-RC.2 no longer includes my hostname entries.
I have two satellite SCALE systems linked with WireGuard to my Core server. I'd been using the Hostname Database to allow replication tasks to target simple hostnames in case I ever need to update their IPs.
Each of the remote systems stopped replicating after the upgrade to 22.02-RC.2, with an inscrutable error message. (Inscrutable enough that I should probably file a separate issue for the message itself.)
The UI and the CLI continue to show my entries. They're just not rendered into /etc/hosts.
I presume this regression is attributable to and its PR#7715.