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, do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Pre-release version
Fedora 22 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 22 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).

Release Notes

Read the F22_Alpha_release_announcement 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

Upgrading with Fedup fails at upgrade prep complete, switching root...

link to this item - Bugzilla: #1185604

Attempting to upgrade to Fedora 22 using FedUp is known to fail due to an issue between fedup, systemd, and SELinux. The upgrade process will fail after you download all the updated packages and reboot into the upgrade process. The failure will not cause any problems with the existing installation (at the point of failure, the upgrade process has not yet begun).

It is possible to work around the issue by adding the kernel command line parameter selinux=0 when booting the upgrade process.

Network issues

DHCP lease renewal fails, leading to loss of network connectivity, on Cloud images (and whenever using network service instead of NetworkManager)

link to this item - Bugzilla: #1184173

An issue in the DHCP utilities included in Fedora 22 Alpha means that DHCP lease renewal usually fails when the system is configured to use the network service rather than NetworkManager. This is notably the case on Cloud installations by default, and is also a commonly-used non-default configuration.

A fix for this issue is expected soon. In the mean time, there are various workarounds. You can use NetworkManager or static addressing. In the bug report, Ben Boeckel suggests: "A script [that] see[s] if it can ping the gateway; if it works, sleep, otherwise kill -9 dhclient and ifdown/ifup the interface."

Fedora Server issues

FreeIPA server deployment (via rolekit or otherwise) fails if FreeIPA packages are installed from Server DVD

link to this item - Bugzilla: #1195811

Due to a mistake, two versions of the Tomcat Java Servlet environment ended up on the Fedora 22 Alpha Server DVD. (They are also included in the frozen Alpha tree on the mirrors, but this is rarely used as a package source.) The result is that FreeIPA server deployment will fail (whether or not rolekit is used) if you add any FreeIPA optional package group at install time when installing from the DVD.

To avoid this issue, do not install any FreeIPA optional package group when installing from the DVD ISO. Instead install it only from the network repositories after installation.

Rolekit fails to deploy a Domain Controller, returning error 256

link to this item - Bugzilla: #1199500

Fix released
An update has been released to address this problem. After you update your system in your usual way, and possibly reboot, you should no longer be affected by it.

The selinux-policy package included with Fedora 22 Alpha includes some erroneous denials which prevent deployment of the 'Domain Controller' role. You may run into this issue if you install from the Fedora 22 Alpha Server DVD and immediately attempt to deploy the 'Domain Controller' role. Instead, please update your system as explained in the box above before attempting to use rolectl, or install from the Fedora 22 Alpha Server network install image.

Rolekit fails to deploy a Domain Controller on a virtual machine

link to this item

First, make sure you're not hitting either of the two issues described above.

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.