Due to bug https://bugzilla.redhat.com/show_bug.cgi?id=1125933 it is not possible to connect Satellite 6 to RHEV/oVirt instance that has non self-signed server certificate. Meaning: most production instances. Solution to that problem is pretty straightforward. If we make the CA field editable, users can fix that problem easily by providing the correct CA (or chain of CAs in the correct order). Also we should add more informative text next to the field (Help popup) explaining how this works.
When working on this bug, test also wildcard cert because I believe this is the root issue of the wildcard problem: https://bugzilla.redhat.com/show_bug.cgi?id=1119420
Upstream bug assigned to lzap
Moving to POST since upstream bug http://projects.theforeman.org/issues/7522 has been closed ------------- Lukas Zapletal Applied in changeset commit:e944a1b2146a9617757340d5f592ded031e6fea5.
VERIFIED *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** # rpm -qa | grep foreman foreman-release-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-gce-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el6.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-proxy-1.0-1.noarch foreman-postgresql-1.7.0-0.develop.201410150839gitb948163.el6.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-broker-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-client-cert-1.0-1.noarch foreman-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-ovirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-vmware-1.7.0-0.develop.201410150839gitb948163.el6.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el6.noarch rubygem-hammer_cli_foreman-0.1.3-1.201410151235gitbc8c449.el6.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el6.noarch foreman-proxy-1.7.0-0.develop.201410101404git7961640.el6.noarch qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-client-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch foreman-compute-1.7.0-0.develop.201410150839gitb948163.el6.noarch ruby193-rubygem-foreman-tasks-0.6.10-1.el6.noarch foreman-libvirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch able to connect Satellite 6 to RHEV/oVirt instance also the CA field is editable
VERIFIED against z-stream
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2014:1857
As far as I checked this fix was not merged to satellite 6.0.6 reopening the issue to verify that it gets to latest available 6.0.z
temp move to MOD for ET
CLOSING as this was included in a prior errata and can't be included in more than one Errata over time. Cloned to https://bugzilla.redhat.com/show_bug.cgi?id=1173228