Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Problem appears with clean install on RHEL 6.7 too. Downgrade ruby193-rubygem-actionpack from version 3.2.8-16 to 3.2.8-13 will help.

(In reply to Milan Zelenka from comment #2)
> Problem appears with clean install on RHEL 6.7 too. Downgrade
> ruby193-rubygem-actionpack from version 3.2.8-16 to 3.2.8-13 will help.

Ran into this problem on a clean install of RHEL 7.2.

Downgrade of ruby193-rubygem-actionpack to 3.2.8-13 resolved our issue as well.

This is a duplicate of BZ 1319771 which has been fixed for 6.1.8.

*** This bug has been marked as a duplicate of bug 1319771 ***