Red Hat Bugzilla – Bug 865942
Last modified: 2012-12-06 02:27:02 EST
Description of problem:
nightly installation cd from 2012-10-09.
selected manual partitioning and my /dev/sda1 that still contains fedora 17 /.
installer fails, log says could not read the crypttab file.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
:The following was filed automatically by anaconda:
:anaconda 18.14 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 860, in _save_right_side
: device_type = device_type_map[device_type]
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1636, in on_selector_clicked
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 192, in _onSelectorClicked
Created attachment 626277 [details]
Created attachment 626278 [details]
Created attachment 626279 [details]
Created attachment 626280 [details]
Created attachment 626281 [details]
Created attachment 626282 [details]
Created attachment 626283 [details]
Created attachment 626284 [details]
Created attachment 626285 [details]
Created attachment 626286 [details]
Created attachment 626287 [details]
Created attachment 626288 [details]
Created attachment 626289 [details]
Do you still see this with anaconda-18.16? Sorry for the lame default question, but storage changes are going in pretty fast right now so it's worth rechecking.
the installation successfully started and finished as soon as i first mkfs.ext4 the / of the existing fedora 17 installation.
without any files in it i could select the existing / as the target of my feodra 18 installation.
didn't know the installer was still in early stages,
i was rather interested into the bug-report-at-install-time, and that worked flawlessly ;-).
The problem here appears to be that we are allowing you to modify /dev/sr0, which is of course not legal. Do you remember if your old F17 installation reference /dev/sr0 in your /etc/fstab?
# Created by anaconda on Sun Dec 4 04:28:09 2011
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
UUID=a8ae94f9-81c8-4983-a6b6-83894596263f / ext4 defaults,relatime,discard,barrier=1,data=journal,journal_checksum 1 1
UUID=2072db8e-f7dc-4c37-bf96-5a7a3ae5ff01 /home ext4 defaults,relatime,discard,barrier=1,data=journal,journal_checksum 1 2
/dev/disk/by-id/ata-Slimtype_BD_E_DS4E1S_105060498663 /disc udf,iso9660 user,noauto,noexec,nosuid,nodev 0 0
## volatile temporary directory
tmpfs /tmpfs tmpfs mode=3777,noexec,nosuid,nodev 0 0
## fedora tmpfs memory based upgrades
#tmpfs /var/cache/yum/x86_64/18/ tmpfs size=2048M,noexec,nosuid,nodev 0 0
are you sincere with the not legal part?
is there any new dynamic way to permit non-root-users to mount optical media without any gnome mounting magic in the background?
this 'user,noauto' stuff worked for ages... suddenly declaring it "forbidden or we crash" is kind of funny.
By "not legal", I mean anaconda should not let you modify a CD/DVD drive as if it were a partitionable device. We've never let you use such devices in the UI before
I don't know anything about any gnome mounting background magic.
i'm confused... i did not *select* any DVD drive at all.
i did select an existing fedora 17 installation that happens to have a fstab entry of an optical media... and the installer of f18 crashed.
on upgrades the installer is perfectly fine to parse configuration files of my existing installations, but in installation mode and manual partitioning?
additionally configuration file parsing that crashes on unexpected values is weird... recalling "always sanitize your input".
> additionally configuration file parsing that crashes on unexpected values is
> weird... recalling "always sanitize your input".
Well, that's why this is a bug report.
anaconda-18.21-1.fc18 has been submitted as an update for Fedora 18.
Package anaconda-18.21-1.fc18, pykickstart-1.99.21-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.21-1.fc18 pykickstart-1.99.21-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
anaconda-18.32-1.fc18, pykickstart-1.99.22-1.fc18 has been submitted as an update for Fedora 18.
pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.