Hide Forgot
Tracking rebuild of ipa-server-docker.
IPA-server-Version: ipa-server-4.4.0-14.el7_3.4.x86_64 IPA-client version: ipa-client-4.4.0-14.el7_3.4.x86_64 Atomic host status: State: idle Deployments: ● rhel-atomic-host:rhel-atomic-host/7/x86_64/standard Version: 7.3.2 (2017-01-13 22:00:41) Commit: 96826a0d917d7ff10f9fd0289581649f2ffbddd76f3b80efd3d95cc11915cacb OSName: rhel-atomic-host Verified the bug on the basis of following points: 1. Verified that ipa-docker can be setup successfully. 2. Verified that replica-docker can be setup successfully. 3. Verified that sssd-container image can be setup as IPA client successfully. 4. Verified that IPA-client normal can be configured successfully against IPA-docker server. 5. Verified that Replica normal can be configured successfully against IPA-docker server. 6. Verified that KRA / vault can be setup on IPA-docker image successfully. 7. Verified that IPA server can be successfully uninstalled from IPA-docker image. 8. Verified that Replica server can be successfully uninstalled from IPA-docker image. Thus on the basis of above observations, marking the status of bug to "VERIFIED".
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:0129