Hide Forgot
Description of problem: My home router hands out automatically generated, and very long, hostnames to devices it doesn't recognise, like newly created vms. These will be something like: anaconda-linux-my-whole-mac-address-as-hex-with-hyphens-in-between-each-hex-couplet.home It's not exactly pretty, but there's nothing wrong with it. The problem is, anaconda seems to use the hostname for automatic device name generation. Allowing it to attempt auto-creation of LVM devices, for example, explodes instantly in an unrecoverable fireball of doom and despair. Until I twigged that the problem when the hostnames, my F23 installation experience was: virt-manager, enter http, create disk Anaconda: select UK english. Click 'Go' or 'Done' or whatever the 'just get on with it' default is. Backtrace of doom, do not retry, do not explain why, do not collect £200. This has made me pretty grumpy with Anaconda for quite a long time. In fact, it has forced me to use btrfs, which it turns out is also somewhere we don't want to send users we want to retain. If I set the hostname to something shorter, device name generation works fine. Incidentally, you can't even do this manually. If the hostname is too long and you go into the disk creation screen, there's absolutely no way back out again. You can't complete the process because even when creating partitions manually it auto-generates device names that it doesn't accept. You're just stuck. Version-Release number of selected component (if applicable): Whatever's in the release images for F23 How reproducible: Always
Please attach the logs from /tmp to this bug as individual, text/plain attachments.
This is trivial to reproduce: just set an absurdly long hostname. I'm not sufficiently invested in it to set up a reproducer right now, as I have a workaround.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.