Common F22 bugs

Click here to set up this language box

This page documents common bugs in Fedora 22 and, if available, fixes or workarounds for these problems. If you find your problem in this page, please do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Release Notes

Read the Fedora 22 release announcement and the Fedora 22 release notes for specific information about changes in Fedora 22 and other general information.

My bug is not listed

Not every bug is listed in this page, but Bugzilla should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and forums.

To see if your bug has already been reported, you can search Bugzilla. If it has not yet been reported, we encourage you to do so to help improve Fedora for yourself and others. A guide to Bugs and feature requests has been prepared to assist you.

If you believe an already-reported bug report should be added to this page because it is commonly encountered, you can:

• Add it yourself, if you have wiki access. Common bugs instructions provides guidance on how to add an entry to the page correctly, but the most important thing is to make sure that the bug is listed - don't worry if you don't get the format quite right, we can clean it up later.
• Or, add the CommonBugs keyword to the bug report. Someone from the QA team will then inspect the issue to determine whether the bug should be listed as a common bug. To expedite your request, please add a comment to the bug that includes
  1. a summary of the problem
  2. any known workarounds
  3. an assessment on the impact to Fedora users

For reference, you can query Bugzilla for bugs tagged CommonBugs:

• CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to this page)
• CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)

Upgrade issues

Fedup is not part of the Alpha criteria and at this time is not functioning with the system in permissive or enforcing modes, this is being tracked in BZ#1185604 .

Fedora Server issues

Rolekit fails to deploy a Domain Controller if FreeIPA packages were included at anaconda install-time

link to this item

There are two issues with Rolekit deploying a domain controller role on Fedora 22 Alpha that have been fixed for Fedora 22 Beta. The first is a packaging mistake that ended up on the DVD. Two versions of the Tomcat Java Servlet environment ended up on the DVD ISO and network install tree. The result is that rolekit will be unable to install correct FreeIPA packages directly from the DVD. As a workaround, do not install FreeIPA from the DVD ISO and instead install it only from the network repositories after installation.

Rolekit fails to deploy a Domain Controller, returning error 256

link to this item

In addition, there was an SELinux bug that was fixed just after the release of Fedora 22 Alpha, but requires an update of the 'selinux-policy' package. Please run dnf update selinux-policy' with access to the network repositories before attempting to use rolectl or the Domain Controller role will fail to install.

Rolekit fails to deploy a Domain Controller on a virtual machine

link to this item

First, make sure you're not hitting the SELinux issue described above. If you're installing on Fedora 22 Beta or later, this will not be an issue.

Creation of a Domain Controller role requires the system to have a sufficient amount of entropy available to securely create the keys for the included certificate authority and Kerberos key distribution center. It is very common when deploying on a virtual machine that has just been created that there will not be sufficient entropy available, which will result in the Domain Controller deployment timing out waiting on /dev/random and then failing with error code 256.

On VM hosts that support it (such as KVM on Fedora 20 and later or RHEL 7.1 and later), it is recommended to create the VM using the virt-RNG device (which the Fedora Server 22 guest will automatically detect). This will allow it to collect entropy from the host machine and should reduce the likelihood of encountering this issue. As a workaround (if you do not have a host capable of providing entropy), you can also run su -c '/usr/sbin/rngd -r /dev/urandom' to make the system use the less-secure /dev/urandom entropy device.

For an in-depth explanation of entropy issues and how they can be resolved, see this excellent blog post: http://rhelblog.redhat.com/2015/03/09/red-hat-enterprise-linux-virtual-machines-access-to-random-numbers-made-easy/