Bug 971179

Created attachment 757390 [details]
File: anaconda.log

Created attachment 757391 [details]
File: backtrace

Created attachment 757392 [details]
File: environ

Created attachment 757393 [details]
File: ifcfg.log

Created attachment 757394 [details]
File: lsblk_output

Created attachment 757395 [details]
File: nmcli_dev_list

Created attachment 757396 [details]
File: packaging.log

Created attachment 757397 [details]
File: program.log

Created attachment 757398 [details]
File: storage.log

Created attachment 757399 [details]
File: syslog

Created attachment 757400 [details]
File: anaconda-tb

I created a user account and then set the root password. The error occurs just after clicking the 'continue configuration' button. After a few seconds the advert banner at the bottom of the screen appeared. Next thing the "error ocurred" message appears.

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019\x20x86_64 rd.live.check quiet BOOT_IMAGE=vmlinuz 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
package:        anaconda-19.30.13-1
product:        Fedora
reason:         OSError: [Errno 2] No such file or directory
release:        Cannot get release name.
version:        19

Russell, does this problem still occur with the F19 release? It looks like anaconda failed to run authconfig, but the packaging.log shows that authconfig was installed, so I'm not sure what's going on.

This problem while I tried to install fedora 19 on vmplayer 5.2 version. 
I tried two times and the same error came and the installation failed.
The installation failed while installing the bootloader

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019\x20x86_64 quiet ks=cdrom:/dev/cdrom:/ks.cfg BOOT_IMAGE=vmlinuz 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
package:        anaconda-19.30.13-1
product:        Fedora
reason:         OSError: [Errno 2] No such file or directory
release:        Cannot get release name.
version:        19

Install F19
- /var, /tmp, /swap, /home on HDD with LVM from existing (F19) system
- / new created as ext4 on SSD
bootloader on SSD

At installing bootloader stage, pressing configuration button (lower right) it crashed

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
package:        anaconda-19.30.13-1
product:        Fedora
reason:         OSError: [Errno 2] Datei oder Verzeichnis nicht gefunden
release:        Cannot get release name.
version:        19

Was installing Fedora 9 x86_64 on VMware 9. My machine is x86_64 compatible.
Virtual Disk was created (7GB ). 
All sda's were created and the complete option too was displayed; sfter that this error was shown.

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019\x20x86_64 quiet ks=cdrom:/dev/cdrom:/ks.cfg BOOT_IMAGE=vmlinuz 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
package:        anaconda-19.30.13-1
product:        Fedora
reason:         OSError: [Errno 2] No such file or directory
release:        Cannot get release name.
version:        19

Hard to tell what's wrong...

cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file:   initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-i686-19-1 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0  BOOT_IMAGE=vmlinuz0 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.i686
other involved packages: python-libs-2.7.5-1.fc19.i686
package:        anaconda-19.30.13-1.fc19.i686
product:        Fedora
reason:         OSError: [Errno 2] Aucun fichier ou dossier de ce type
release:        Fedora release 19 (Schrödinger’s Cat)
version:        19

My second install attempt succeeded. What I did differently:
- Use standard partitions instead of BTRFS subvolumes (in the first attempt, I asked for one volume called fedora on which I put both / and /home).
- Use a strong password for root.
- Only set root password after the install completed (i.e. button to finish configuration appeared).
- Did not create any normal user.

So one of these changes fixed the bug.

I have got the same issue, and this didnt resolve it.
(In reply to Milan Bouchet-Valat from comment #18)
> My second install attempt succeeded. What I did differently:
> - Use standard partitions instead of BTRFS subvolumes (in the first attempt,
> I asked for one volume called fedora on which I put both / and /home).
> - Use a strong password for root.
> - Only set root password after the install completed (i.e. button to finish
> configuration appeared).
> - Did not create any normal user.
> 
> So one of these changes fixed the bug.

22:12:04,571 DEBUG packaging: Traceback (most recent call last):
22:12:04,572 DEBUG packaging: File "/usr/libexec/anaconda/anaconda-yum", line 178, in callback
22:12:04,572 DEBUG packaging: return func(amount, total, key, data)
22:12:04,572 DEBUG packaging: File "/usr/libexec/anaconda/anaconda-yum", line 277, in inst_open_file
22:12:04,573 DEBUG packaging: os.unlink(txmbr.po.localPkg())
22:12:04,574 DEBUG packaging: OSError: [Errno 30] Read-only file system: '/run/install/repo/Packages/s/schroedinger-cat-backgrounds-base-18.90.0-1.fc19.noarch.rpm'
22:12:04,575 DEBUG packaging: FATAL ERROR: python callback <bound method RPMCallback.callback of <__main__.RPMCallback object at 0x7f4c6aa470d0>> failed, aborting!

Something happened to set the filesystem to read only so it couldn't finish the install. I'd expect to see errors in syslog, but there is nothing there.

As for the 'dupes' of this error, if you don't have   iutil.execWithRedirect("/usr/sbin/authconfig", args, root=ROOT_PATH) in your traceback, please open a new bug with the anaconda-tb-* file attached to it -- the abbreviated reports don't really tell us anything.

ABRT should be fixed to upload the full data then. Of course now I cannot wipe my whole system just to try reproducing the bug and possibly give you some information. When install errors happen and a user reports them, all possible information should be saved when it's still available...