Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
VERIFIED: rpm -qa | grep foreman ruby193-rubygem-foreman_docker-1.2.0.11-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.19-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch foreman-debug-1.7.2.19-1.el6_6sat.noarch foreman-1.7.2.19-1.el6_6sat.noarch foreman-libvirt-1.7.2.19-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch foreman-proxy-1.7.2.4-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.11-1.el6_6sat.noarch puppet-foreman_scap_client-0.3.3-8.el6_6sat.noarch foreman-compute-1.7.2.19-1.el6_6sat.noarch foreman-gce-1.7.2.19-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch foreman-vmware-1.7.2.19-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch foreman-postgresql-1.7.2.19-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.5-1.el6_6sat.noarch steps The Administer -> About page talks about satellite 6 Links leads to Red Hat documentation and support channels as well
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.