Bug 894408 - Completely broken anaconda installer on "complicated" partitions
Summary: Completely broken anaconda installer on "complicated" partitions
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-11 16:52 UTC by jiri vanek
Modified: 2013-08-22 18:06 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-22 18:06:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
trace from one of the crashes (2.35 MB, text/plain)
2013-01-11 16:52 UTC, jiri vanek
no flags Details

Description jiri vanek 2013-01-11 16:52:23 UTC
Created attachment 676989 [details]
trace from one of the crashes

How to reproduce
 - create several logical volumes  on LVM managed system and left some free space
 - execute some liveiso of RC4 (is there since RC1 when I started to try to install it).
 -Try to install to the freespace or to some fresh volume.
 - in most cases the advance dialog show you something, but not what you want, 
   the simple dialogue will be useless completely
 - if you will spend some time in installer it will soon crash with exception like in https://bugzilla.redhat.com/show_bug.cgi?id=882615
  - xfce spin will not even start installer (again similar crash, and also crash in reporrt bug dialogue )
 

-expected result - I will be allowed to select correct volume or free space where to install

My testing environment and steps are described lower, msivak or anybody from CZ anaconda team can come and try it on his own:

I have PC with LVM, each logical volume have its own operating system (fedoras, rhels):

ENVIRONEMT start------------------------------------------------
[root@localhost ~]# lvm
lvm> lvscan 
  inactive          '/dev/VolGroup/lv_root' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/SharedSpace' [20.00 GiB] inherit
  inactive          '/dev/VolGroup/f15_86fs' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_32' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_64' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/f16x86' [29.30 GiB] inherit
  inactive          '/dev/VolGroup/f17_86fs' [29.30 GiB] inherit
lvm> vgdisplay 
  --- Volume group ---
  VG Name               VolGroup
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  11
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                7
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               465.27 GiB
  PE Size               4.00 MiB
  Total PE              119109
  Alloc PE / Size       60120 / 234.84 GiB
  Free  PE / Size       58989 / 230.43 GiB
  VG UUID               D6d8mz-AGar-G43F-1uT2-cerv-UBbh-4bUq0s



[root@localhost ~]# fdisk  /dev/sda -c
Welcome to fdisk (util-linux 2.22.1).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c00c3

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1026047      512000   83  Linux
/dev/sda2         1026048   976773119   487873536   8e  Linux LVM


ENVIRONEMT END------------------------------------------------
Rest of the space is unused. Howerer anacond ainnstaller was complaining about no space avaiable and was not able to offer me free space or to allow me to create new lvm volume.

After feew click I have got into  https://bugzilla.redhat.com/show_bug.cgi?id=882615

The I have added partition manually:

ENVIRONEMT START------------------------------------------------

  inactive          '/dev/VolGroup/lv_root' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/SharedSpace' [20.00 GiB] inherit
  inactive          '/dev/VolGroup/f15_86fs' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_32' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_64' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/f16x86' [29.30 GiB] inherit
  inactive          '/dev/VolGroup/f17_86fs' [29.30 GiB] inherit
  SOMETHING_SORRY_DONOTREMBER          '/dev/VolGroup/fedora-18-x86_64' [20.00 GiB] inherit
ENVIRONEMT END------------------------------------------------

Anaconda have not survived it, crashed completel (with something similar toi 882615)
reboot and attempt two. Now anaconda behaved little bit better, it found that there is free space, but have not allowed me any manipulation on free space. Also it have not allowed to to touch the new partition.

ENVIRONEMT start------------------------------------------------
po rebootu:
  inactive          '/dev/VolGroup/lv_root' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/SharedSpace' [20.00 GiB] inherit
  inactive          '/dev/VolGroup/f15_86fs' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_32' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/Rhel51_64' [39.06 GiB] inherit
  inactive          '/dev/VolGroup/f16x86' [29.30 GiB] inherit
  inactive          '/dev/VolGroup/f17_86fs' [29.30 GiB] inherit
  inactive          '/dev/VolGroup/fedora-18-x86_64' [20.00 GiB] inherit
ENVIRONEMT END------------------------------------------------


After some attemps the installer crashes again with known bug number above.

Please note, all attempts are just click on button "show disks" and "cancel" nothing more, no real work.

As I told, brno anacodna team can come and try.

Comment 1 Chris Lumens 2013-01-18 15:51:59 UTC
Reassigning for investigation.

Comment 2 David Lehman 2013-06-13 20:37:10 UTC
Please take a look at the fedora installation guide's partitioning section, then try again to install. If you continue to see problems, please report specific failures with logs and either screenshots or, if possible, screencasts.

Comment 3 David Lehman 2013-08-22 18:06:43 UTC
See comment 2.


Note You need to log in before you can comment on or make changes to this bug.