RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1460207 - Respin 7.3.6
Summary: Respin 7.3.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa-server-container
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Vobornik
QA Contact: Nikhil Dehadrai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-09 11:19 UTC by Standa Laznicka
Modified: 2017-06-28 15:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-28 15:45:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1644 0 normal SHIPPED_LIVE Red Hat Enterprise Linux Atomic Identity Management Server Container Image 2017-06-28 20:04:06 UTC

Description Standa Laznicka 2017-06-09 11:19:46 UTC 
Regular respin
Comment 3 Nikhil Dehadrai 2017-06-23 17:31:00 UTC 
IPA server : ipa-server-4.4.0-14.el7_3.7.x86_64
IPA-Client Version: ipa-client-4.4.0-14.el7_3.7.x86_64
ipa-server-docker image: ipa-server-docker-4.4.0-45

atomic host status:
State: idle
Deployments:
● atomic-host:rhel-atomic-host/7/x86_64/standard
             Version: 7.3.6 (2017-06-22 22:52:36)
              Commit: 692aa8cada83b0a3fc51ea423abcfc7de585e4200f3a87d76f1ce379d46068b1


Verified the bug with following scenarios:
1. Verified that IPA-server is installed through ipa-docker image.
2. Verified that IPA-replica is installed through ipa-docker image.
3. Verified that klist command works both on ipa-server/ipa-replica configured through ipa-docker image.
4. Verified that 2-way trust can be setup with windows AD with IPA-server configured through ipa-docker image.
5. Verified that IPA-client configured with sssd-container image can be setup against this IPA-server.
6. Verified that non-containerized IPA-client can be setup against this IPA-server.
7. Verified that sudo rules work for IPA-server  installed through ipa-docker image.
8. Verified that latest version of ipa-server is available with ipa-docker image.
9. Verified that IPA-server UI us accessible when it is installed through ipa-docker image.
10. Verified that command ipa-adtrust-install, ipa-kra-install, ipa-vault-add run successfully
11. Verified that IPA-server/ IPA-replica server can be uninstalled.

Thus on the basis of above observations marking status of bug to "VERIFIED".
Comment 6 errata-xmlrpc 2017-06-28 15:45:41 UTC 
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:1644
Note You need to log in before you can comment on or make changes to this bug.