+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1490041 +++ ====================================================================== Description of problem: To integrate cockpit certificate signing and SSO with Red Hat IdM RHVH needs to include ipa-client rpms. Also, looking to apply ansible playbook to generate certificate and need ansible user to kinit on host with keytab. These require that the rhvh host be part of the IdM realm. This is not simple without the IdM client. I am not aware of a restriction in the implementation of rhv that prevents this. Version-Release number of selected component (if applicable): 4.2.0 How reproducible: Always. Steps to Reproduce: 1. Install hypervisor 2. Try to install ipa-client 3. Fail Actual results: Package not available Expected results: Package installs Run and configure ipa-client using ipa-client-install Additional info: (Originally by Paul Armstrong)
Is this a bug or feature request? Is it upstream or comes from a customer? What's the severity? (Originally by Yaniv Kaul)
Test steps: rhvh-4.1-0.20170914.0+1 Test steps: 1. Install hypervisor 2. Register to RHSM 3. Try to install ipa-client Test result: ipa-client package not available. (Originally by Chen Shao)
We'll target this as a multi product errata shipped in the RHVH channel rather than including it as part of the image. (Originally by Ryan Barry)
Yuval - can you please take care of a multi-product errata for this? (Originally by Ryan Barry)
Waiting for PM approval since this will pull in more than 60 packages. I'm conditionally nacking this bug on design, since I don't think it's a good design to tag so many packages into rhv-h channel. (Originally by Sandro Bonazzola)
ipa-client is shipped within rhel-7-server-rpms channel so we can just include it. (Originally by Sandro Bonazzola)
# yum list redhat-release-virtualization-host ipa-client Installed Packages ipa-client.x86_64 4.5.0-21.el7_4.2.2 installed redhat-release-virtualization-host.x86_64 4.1-8.1.el7 installed
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-2017:3431