This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2136169 - better error should be thrown when invalid character is in hostname
Summary: better error should be thrown when invalid character is in hostname
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-19 13:55 UTC by Vladimir Benes
Modified: 2023-08-17 09:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 09:21:51 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-159 0 None None None 2023-01-24 08:33:50 UTC
Red Hat Issue Tracker   RHEL-1405 0 None None None 2023-08-17 09:21:50 UTC
Red Hat Issue Tracker RHELPLAN-137042 0 None None None 2022-10-19 14:05:59 UTC

Description Vladimir Benes 2022-10-19 13:55:23 UTC 
Description of problem:
$ sudo nmcli general hostname ng_benjoband
(15:41:10) vbenes: Error: failed to set hostname: Saving the hostname failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid static hostname 'ng_benjoband'

While we have just [a-z] [0-9] and - allowed, NM should check first before sending via dbus and tell the user what's wrong. 

Version-Release number of selected component (if applicable):
NetworkManager-1.40.0-1.el9.x86_64
Comment 2 RHEL Program Management 2023-08-17 09:21:19 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Note You need to log in before you can comment on or make changes to this bug.