Failure to assign user selected hostmame

Bug #1864352 reported by Leó Kolbeinsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Calamares
Fix Released
Unknown
calamares (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Failure to assign user selected hostmame

The installer asks for the computer name but assigns to all machines the hostname "linux"

I found this on 3 installs =in a VirtualBox,on Dell Inspirion 3521 and Intel NUC 8i3BEK

This was FOCAL Lubuntu daily build 22022020

Attached is the session log for the Intel NUC install - the user requested the computer name = straumssel and after reboot the hostmane was "linux"

Tags: iso-testing
Revision history for this message
Leó Kolbeinsson (leok) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1864352

tags: added: iso-testing
Changed in calamares (Ubuntu):
status: New → Confirmed
Changed in calamares:
status: Unknown → New
Changed in calamares (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

There were changes in 3.2.19 that added functionality to specify the mechanism to set the hostname. None of them appear to work at all. The theory is this is because there's already an /etc/hostname. Curiously the log provides no information other than it seems to start the job but provides no information about it ending, whether as a failure or success.

Should be fixed in 3.2.19.1.

BTW Leó you should use `ubuntu-bug «package-name»` and it will automatically pull in diagnostic information such as the session log.

Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

3.2.19.1 is not available in proposed and should resolve this.

Changed in calamares (Ubuntu):
status: Triaged → Fix Released
Changed in calamares:
status: New → Fix Released
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Tested 3.2.19.1 in VirtualBox machine plus Dell inspirion 3521 and an Intel NUC8i3BEK and can confirm that the hostname issue appears to be resolved.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.