Description of problem: Anaconda crashes directly on startup. This happens reliably after I installed Fedora on a fwraid disk (with updates.img from bug 1156354 and bug 1156614), and then destroyed that array in bios (I'm not sure whether that erases those disks' contents or not), while keeping them still set in "raid mode" instead of "ahci mode" in configuration. Version-Release number of selected component: anaconda-21.48.12-1 The following was filed automatically by anaconda: anaconda 21.48.12-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 944, in addUdevPartitionDevice raise DeviceTreeError("failed to scan disk %s" % disk.name) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1201, in addUdevDevice device = self.addUdevPartitionDevice(info) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2170, in _populate self.addUdevDevice(dev) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2105, in populate self._populate() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 479, in reset self.devicetree.populate(cleanupOnly=cleanupOnly) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 183, in storageInitialize storage.reset() File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) DeviceTreeError: failed to scan disk sdb Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: inst.repo=nfs:nfs.englab.brq.redhat.com:/pub/fedora/fedora-alt/stage/21_Beta_RC1/Server/x86_64/iso/Fedora-Server-DVD-x86_64-21_Beta.iso initrd=F21/Beta_RC1/x86_64/initrd.img BOOT_IMAGE=F21/Beta_RC1/x86_64/vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.1-302.fc21.x86_64 product: Fedora" release: Cannot get release name. type: anaconda version: Fedora
Created attachment 950978 [details] File: anaconda-tb
Created attachment 950979 [details] File: anaconda.log
Created attachment 950980 [details] File: environ
Created attachment 950981 [details] File: lsblk_output
Created attachment 950982 [details] File: nmcli_dev_list
Created attachment 950983 [details] File: os_info
Created attachment 950984 [details] File: program.log
Created attachment 950985 [details] File: storage.log
Created attachment 950986 [details] File: syslog
Created attachment 950987 [details] File: ifcfg.log
Setting the disks to "ahci mode" did not help. The only thing that made anaconda not crash was a) creating the raid5 volume again b) hard-erasing those disks with dd, before starting anaconda I assume this is quite inconvenient, because until you erase/reformat your disks, anaconda is not able to start on a machine with a previously existing and then destroyed raid volume. I assume this violates some partitioning criteria, maybe this one: https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria#Custom_partitioning " Remove existing storage volumes " because that's what you would want to do with those disks - remove existing (now invalid) data and perform a new installation.
(In reply to Kamil Páral from comment #11) > Setting the disks to "ahci mode" did not help. The only thing that made > anaconda not crash was > a) creating the raid5 volume again > b) hard-erasing those disks with dd, before starting anaconda To be exact here, this is a) OR b). Either I had to create the raid volume again, or leave it raid-less, but wipe the disks.
Discussed at 2014-10-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-27/f21-blocker-review.2014-10-27-16.01.log.txt . This certainly seems like a potential blocker, but we wanted to check if I can reproduce it, have kparal test a few other things, and get input from the anaconda devs before making a final call, so we agreed to delay the decision and vote in Bugzilla later.
I have tried the same approach, but this time with RAID 0, and anaconda did not crash on start. So either this is specific to RAID 5, or it is not deterministic. Investigating more.
When playing with this more, I noticed that at the end of the installation mdadm crashed, probably due to selinux denial. See bug 1157770 and bug 1157774.
I tested once again with RAID 5 and I can't reproduce the bug anymore. Sigh. Anaconda does not crash, the disks look empty, and installation starts OK. So -1 blocker on this bug, it's not deterministic and might be hard to hit. Of course, unless the devs say otherwise and can find the problem easily.
Discussed at 2014-10-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-27/f21-blocker-review.2014-10-27-16.01.log.txt . Based on the info that kparal could not reproduce it we voted -1 blocker for now; he and I will both try some more and re-propose if it seems warranted.
sdb has a corrupt gpt disklabel on it. The kernel is happy with the backup, so sdb1 exists. I recently changed blivet to not act like it's okay to have a partition on an unpartitioned disk, thus the exception/traceback. This is a difficult situation to handle non-interactively, but I don't feel too bad forcing you to make sdb consistent before doing an OS installation on it.
OK. I'm not sure how I ended up with a corrupt gpt disklabel on sdb, because I installed fedora on a fwraid 5 comprised of sda + sdb + sdc (and then destroyed the raid). Shouldn't the disklabel be present on sda only? Or, perhaps, could it be somehow partially present because of the raid distributing data across the disks? Can it be a remnant of a previous installation (start of the disk overwritten when creating the raid, but not the end, therefore backup table still present)? Anyway, a possible improvement here would be to tell the user "sdb has a corrupt partitioning table, please reformat the disk in an external application and run the installer again". Of course that's probably a bit more difficult than it sounds :) If you have no planned improvements in this area, let's close this bug (but showing at least some basic message and then force quitting would definitely be nicer than crashing).
I have proposed patches to announce the situation to the user and give them an opportunity to fix it in the installer's shell before retrying the storage scan or exit the installer and fix it some other way.
Another user experienced a similar problem: I was trying to install Fedora 21 Beta and launched "Install To Disk" from panel on left side of screen. It displayed an error message notification at the bottom then started and then 2-3 error dialogs on top of anaconda window. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Workstation-x86_64-2 ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 3.17.1-302.fc21.x86_64 other involved packages: python-blivet-0.61.8-1.fc21.noarch, python-libs-2.7.8-4.1.fc21.x86_64 package: anaconda-core-21.48.13-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Hung at probing devices cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdd release: Fedora release 21 (Twenty One) version: Fedora
*** Bug 1168038 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Hardware: HP Proliant ML350 Gen 5, dual quad core xeon E5430, 16gb ram, HP SmartArray E200i RAID controller Disks: (no multi-disk RAID arrays setup) 500GB planned for Fedora, 1TB planned for /home, and 500GB planned for backup Brief history: I have been experiencing issues with the Anaconda installer ever since Fedora 20 on the ML350. I previously had a plain Dell Poweredge 840 w/ F20 and Anaconda ran smoothly when I installed it. For F20 on the ML350, I used the same install disk but kept on getting the "pane is dead" error (or a similar, more obscure error when installing from the live CD). I did verify the install media was okay. I was able to get around that by following the last paragraph in paragraph #6 of Bug #1084888. Step by step: 1) Boot from Fedora 21 server edition DVD 2) Test media and install (or install via basic graphics, it doesn't make a difference) 3) "An unknown error has occurred" ... 4) If you click "exit", the window hangs forever Can be reproduced every time. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-21-x86_64 nomodeset quiet hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 package: anaconda-21.48.21-1 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk cciss/c0d1 release: Cannot get release name. version: Fedora
anyone hitting this, please see https://bugzilla.redhat.com/show_bug.cgi?id=1157657#c18 .
Ah, it took me several re-reads of comment 18 here to figure out what was really going on! (Thanks for the pointer Adam). The disks I'm using in my ML350 were previously used for other things...so I assumed the installer would just mark them as "unknown partition" and give me an option to clean and re-partition the disks. Upon hitting the error message, I switched to tty2 (Alt+Ctrl & F2) and ran "parted -l". Two disks came up as "Unknown partition table" and the third came up as an unknown MSDOS partition and a warning saying "can't have partition outside the disk". I just created new gpt tables on all 3 disks (via parted mklabel in tty2), rebooted, and the installer launches! Thanks Adam and David!
Another user experienced a similar problem: Just started install process. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 ro rd.live.image quiet rhgb rd.live.check hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Booted Fedora 21 Workstation Live DVD, Selected Install to Hard disk, Got error. Happens every time. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Opening the installer, computer with windows 8.1, GPT. installer from USB and DVD cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz0 root=live:LABEL=LIVE ro rd.live.image quiet rhgb hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdb release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Error occured trying to do a fresh Fedora 21 Workstation install using the most recent live media. It looks like it cannot scan my hard drives. I have 3 hard drives. One held a previous linux OS and 2 were configured as a RAID 1 array using MDADM cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdb release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Trying to install Fedora 21 LXDE Spin cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-LXDE-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdb release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: This issue arose when trying to install fedora on my laptop. I was able to boot to live USB without issue, but when I went to install Fedora to my hard drive it instantly gave me this error. I tried the main Fedora Distribution before this with the same result. This is the KDE version of Fedora. I believe it may be an issue with my drive. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-KDE-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
*** Bug 1177674 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: I created a LiveCD and booted from it. Fedora took about 10 minutes to come up, but I was given the option to install Fedora on my laptop. When I selected the option to install Fedora on my laptop, I received an unknown error. In the background, I can see the first install screen to select a language...but the error message only gives me two option: report bug or quit. My laptop is an Lenovo W520 with 64 MB of RAM and a 512 GB flash drive. I wish I could give more detail, but I don't get very far in the installation. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: anaconda 21.48.21-1 exception report. This is the error I am getting all the time, when I am trying to boot Fedora 21 into my hard drive. Comments: Fedora Live is running smoothly but the booting into hard drive shows this error. My motherboard is ASRock H81M-S1 Plus which is a fourth generation motherboard supporting Intel Haswell processor technology. My processor is Intel G3220 LGA1150. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Just selected install to hard disk after bootinh fedora 21 "live" cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 nomodeset hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdc release: Fedora release 21 (Twenty One) version: Fedora
*** Bug 1174274 has been marked as a duplicate of this bug. ***
*** Bug 1188019 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Clicked on install to hard drive from Live USB cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
I don't have a problem with forcing the user to fix a disk before installing Fedora if Fedora is supposed to be installed on that particular disk. But I do have a problem when Fedora refuses to install on a perfectly valid disk if there is another corrupt disk present. In my case I had two disks, and i couldn't install Fedora on the valid disk until I physically unhooked the bad disk.
Maybe one solution would be to check all disks and present the user with only the valid ones for the partitioning step and ignore the bad ones or mark them unsuitable for the install.
Another user experienced a similar problem: failed to scan disk cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=(loop)/isolinux/vmlinuz0 iso-scan/filename=/Fedora/Fedora-21-LXF-Remix-x86_64.iso root=live:CDLABEL=Fedora-21-LXF-Remix-x86_64 rootfstype=auto ro quiet rd.live.image noeject rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdi release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: I'm installing Fedora on a machine that previously had Debian Jessie (testing) on it. I have full-disk-encrytion on the HD (from the previous install) and I have not yet attempted to remove the existing partitions, I was assuming the installer would just take care of that for me. BIOS is set to UEFI mode and successfully booted from the USB stick (the USB stick is a fast USB 3.0 stick) and the machine has USB 3.0 ports. I've used the 'live-usb' environment for a couple of hours earlier, this problem only appears when I attempt to install. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 ro rd.live.image quiet rhgb rd.live.check hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: It happened installing Fedora to a Hard Drive cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:LABEL=UUI NULL=Fedora-Live-WS-x86_64-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.x86_64 other involved packages: python-blivet-0.61.13-1.fc21.noarch, python-libs-2.7.8-7.fc21.x86_64 package: anaconda-core-21.48.21-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sda release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: When I install Fedora from a USB stick and click the button "click it in disk", It appeared. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-21-5 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.4-301.fc21.i686 other involved packages: python-libs-2.7.8-7.fc21.i686, python-blivet-0.61.13-1.fc21.noarch package: anaconda-core-21.48.21-1.fc21.i686 packaging.log: product: Fedora" reason: DeviceTreeError: failed to scan disk sdb release: Fedora release 21 (Twenty One) version: Fedora
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.