Description of problem: When installing to a disk image, anaconda calls /bin/hostname with the hostname set in the user interface. This is not appropriate. The image install must not modify the configuration of the system it is being run on, but rather configure a separate system within the disk image. Version-Release number of selected component (if applicable): anaconda-17.3-1 How reproducible: Always Steps to Reproduce: 1. Do a disk image install and set a hostname Actual results: The hostname of the system on which you're running anaconda will be changed. Expected results: The hostname of the system on which you're running anaconda remains unchanged. Additional info: This was introduced with the following commit: commit 8563670436f38d8f504ccf1a3e9a4ff95a975acc Author: Radek Vykydal <rvykydal> Date: Tue Dec 7 15:36:55 2010 +0100 Set installer environment hostname for sw raid LABELs (#640743) mdadm tool will use it when creating the device. An alternative fix without the undesirable side-effects would be to pass --homehost= to mdadm when creating new arrays.
Adding to F17Alpha since this should be a fairly quick fix and needs to make F17.
Discussed at 2012-01-27 blocker review meeting. We can't see any impact of this bug on the alpha criteria. dlehman proposed it essentially as a reminder-to-self to get the issue fixed, but unfortunately we can't really use the blocker or nth processes in that way. We recommend use of the priority/severity fields for this purpose instead. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This shouldn't be a problem in git anymore. See pyanaconda/network.py: def setHostname(hn): if flags.imageInstall: log.info("image install -- not setting hostname") return Not that we've really tested image installs, though.