Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Comment 2Djordje Todorovic
2017-03-16 12:09:38 UTC
tang has been added to comps for rhel-7.4 *into group: *directory-server
<group>
<id>directory-client</id>
<_name>Directory Client</_name>
<_description>Clients for integration into a network managed by a directory service.</_description>
<default>false</default>
<uservisible>false</uservisible>
<packagelist>
. . .
<packagereq type="optional">tang</packagereq>
. . .
</packagelist>
</group>
Comment 5Djordje Todorovic
2017-04-25 11:00:32 UTC
I just checked, 'tang' is present in the latest nightly.
Searching in /mnt/redhat/nightly/latest-RHEL-7/
Client/x86_64/os/Packages/tang-4-1.el7.x86_64.rpm
ComputeNode/x86_64/os/Packages/tang-4-1.el7.x86_64.rpm
Server/aarch64/os/Packages/tang-4-1.el7.aarch64.rpm
Server/ppc64/os/Packages/tang-4-1.el7.ppc64.rpm
Server/ppc64le/os/Packages/tang-4-1.el7.ppc64le.rpm
Server/s390x/os/Packages/tang-4-1.el7.s390x.rpm
Server/x86_64/os/Packages/tang-4-1.el7.x86_64.rpm
Workstation/x86_64/os/Packages/tang-4-1.el7.x86_64.rpm
Comment 9Djordje Todorovic
2017-04-28 13:01:15 UTC
tang has been moved to directory-server group (was accidentally added to directory-client group), which should be available on the server variant only.
Author: Djordje Todorovic <dtodorov>
Date: Fri Apr 28 08:57:59 2017 -0400
rhel-7.4: move tang to directory-server (was added to directory-client)
I actually do believe that we want to have it in @directory-server which kinda matches free-ipa. Rather than explicit insertion to just Server.
Adding needinfo to our expert. Please keep it in modified/qe unless he says otherwise.
Thanks
Lubos
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:1850
tang has been added to comps for rhel-7.4 *into group: *directory-server <group> <id>directory-client</id> <_name>Directory Client</_name> <_description>Clients for integration into a network managed by a directory service.</_description> <default>false</default> <uservisible>false</uservisible> <packagelist> . . . <packagereq type="optional">tang</packagereq> . . . </packagelist> </group>