| Summary: | anaconda totally fails with text install; graphical in the same situation works fine | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robin Powell <rlpowell> | ||||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | jonathan, rlpowell, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | anaconda-16.15-1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-07 20:19:59 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
It's expected that the text installer doesn't allow customizing partitioning. However, there shouldn't really be any difference between the drives detected. Can you attach /tmp/storage.log from the text install? How would I get access to that? As far as I know, /tmp is RAM at that point, on the VM, and I don't see how to break out of the installer to get it. -Robin You can use scp. I'm afraid I'm going to need some more detail; at this stage in the install, the system has no network of any kind, so I can't scp in from the outside. The virt-install console mode doesn't accept ctrl-alt-F3 to give me a console window, so I can't scp out from the inside. I could run the kernel with the "rescue" option, but I don't know how to run Anaconda from there in a way that works, so I can't repro in that case. What am I missing? -Robin A friend of mine pointed out that I could use libvirt's VNC stuff with Anaconda still in text mode, so I did that; everything from /tmp is in http://teddyb.org/~rlpowell/media/public/tmp/anaconda_text_mode.tgz for your perusal. -Robin I now know what the problem is. Whether you still consider it a bug when I'm done, I dunno; I doubt it. Mea culpa: I did not actually do a graphical install all the way through when I said it worked, which was shitty/stupid of me. So, these "drives" are LVs on the master host; this is a VM. Let's say that on the master we have /dev/local/foo, which shows up as /dev/vda on the VM. What I want to do is directly mount /dev/vda as / (which makes it easy to mount it as /dev/local/foo on the master if things go sideways with the VM). To that end, I had run mkfs on /dev/local/foo; it was an ext4 LV from the master's perspective. Anaconda has no idea how to deal with this. It sees a drive with no partitions, *and* no free space. It does not appear to have any means to resolve this; no space can be created, even in graphical mode (where at least the drives show up). What I *want*, as I said, is to call /dev/vda my / FS; if y'all want to put in support for that, fantastic; if not, I think this isn't a bug at all and you should just close it. -Robin Ah, so these were drives with filesystems created directly on them? There's no partition tables? It's true - anaconda does not know how to work too well with those. We support reading them but I don't believe you can create them. Reassigning to dlehman since he would have an idea of what we can do and when we can do it. Note that for our current text mode interface, we're not going to be adding partition manipulation stuff there so nothing will change in that respect. Created attachment 513847 [details]
storage.log from affected system
There is a bug here. The text mode code for obtaining the list of disks only uses partitioned disks. I'll bring that code in line with the gui code. Robin, you still won't be able to use a whole disk as your root filesystem. We don't support any direct editing of whole-disk formatting. If you partition the devices on the master system your complaint is that you'll have to run kpartx to get device nodes for the partitions in order to examine the filesystem from outside the vm? For now that's a limitation we cannot avoid. Yeah, pretty much; I didn't know about kpartx when I first opened this. :) It's not really a big deal. -Robin This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 505727 [details] Text mode: no drives for you! I'm going to ignore the ticket template in favour of showing the two different behaviours, the graphical installer and the console installer, in some detail. Please feel free to ask for more details of any kind, or indeed for an account on the system to try it out (although it's a very barebones F15 system, so I can't imagine reproducing this will be hard). There is a chance this isn't an Anaconda problem, but I think it probably is. Master host is a straight F15 system as I said, x86_64, lots of RAM and CPU and disk. I'm making sub-VMs with libvirt/virt-install. They're supposed to use LVs for their disk partitions. In text mode, it simply doesn't work at all. rlpowell@basti> sudo lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert basti_root local -wi-ao 10.00g basti_swap local -wi-ao 2.00g jukni_root local -wi-ao 10.00g jukni_srv local -wi-ao 10.00g jukni_swap local -wi-ao 2.00g Graphical run starts like this: virt-install \ --connect qemu:///system \ --virt-type kvm \ --name jukni \ --ram 2048 \ --disk path=/dev/mapper/local-jukni_root \ --disk path=/dev/mapper/local-jukni_srv \ --disk path=/dev/mapper/local-jukni_swap \ --graphics vnc,port=5900,listen=0.0.0.0 \ --location /var/tmp/Fedora-15-x86_64-netinst.iso \ --os-variant fedora15 And then I connect with VNC. Screens are like so: - language [English] - keyboard [us] [switch to full-on graphical] - basic/advanced storage [basic] - hostname [jukni.digitalkingdom.org] - city [Los Angeles], utc [yes] - root password - Various disk usage options: all space, replace, shrink, free space, custom; checkboxes for encrypt and review and modify the result [all space - shows block devices; 4 of them, virtio block devices (3 plus the CD ISO, as expected); identifiers are virtio-0000:00:0[4567].0-virtio-pci-virtio[1234] (that's typed out by hand so may not be perfectly accurate) The other method goes like this: virt-install \ --connect qemu:///system \ --virt-type kvm \ --name jukni \ --ram 2048 \ --disk path=/dev/mapper/local-jukni_root \ --disk path=/dev/mapper/local-jukni_srv \ --disk path=/dev/mapper/local-jukni_swap \ --extra-args "text console=tty0 console=ttyS0,115200" \ --nographics \ --location /var/tmp/Fedora-15-x86_64-netinst.iso \ --os-variant fedora15 I am then, eventually, presented with a console interface (there's a weird delay at the beginning where I don't see any of the console output and then I get a bunch all at once; perhaps bad buffering?; almost certainly nothing to do with Anaconda). Screens: - language [English] [no keyboard screen??] - zone [Los Angeles], utc [yes] [no hostname screen] - disk storage options screen; F2 for advanced drive options; options are: entire drive, replace, free space; no shrink option, *NO CUSTOM OPTION*, which seems really bad, and no modify-the-result option Unlike the graphical install, his screen shows no drives whatsoever. I can't get past it. There's a section that *should* show drives, but if I go there and hit return or space, the install simply locks up. "Screenshot" attached. -Robin