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 709081 - sssd.$arch should require sssd-client.$arch
Summary: sssd.$arch should require sssd-client.$arch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 709333 748844
TreeView+ depends on / blocked
 
Reported: 2011-05-30 14:53 UTC by Marko Myllynen
Modified: 2018-11-14 09:42 UTC (History)
8 users (show)

Fixed In Version: sssd-1.5.1-40.el6
Doc Type: Bug Fix
Doc Text:
Cause: The sssd deamon package did not explicitly specify that it required sssd-client package of the same architecture Consequence: It was difficult to specify to install both primary and secondary architecture sssd-client packages on multiarch systems. Simply issuing "yum install sssd sssd-client.i686" on a x86_64 system would only install sssd-client.i686 while it should install both x86_64 and i686 systems Fix: The main sssd package requires sssd-client of the same architecture Result: Installing a secodary-arch sssd-client package would bring in the primary architecture sssd-client as well
Clone Of:
: 709333 748844 (view as bug list)
Environment:
Last Closed: 2011-12-06 16:38:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1529 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2011-12-06 00:50:20 UTC

Description Marko Myllynen 2011-05-30 14:53:08 UTC 
Description of problem:
This was discussed over IRC at least once but IMHO was left a bit open.

sssd.x86_64.rpm currently requires sssd-client, not sssd-client.x86_64. sssd.x86_64.rpm is AFAIK unable to work for most if not all use cases without sssd-client.x86_64.rpm. However, some 32-bit applications like acroread require also sssd-client.i686.rpm in order to function.

So basically most common setup would include:

sssd.x86_64.rpm
sssd-client.x86_64.rpm

And if there's a need to support some 32-bit application one could add:

sssd.x86_64.rpm
sssd-client.x86_64.rpm
sssd-client.i686.rpm

The issue was the if one wants to provide the latter in a cross 32/64-bit kickstart file, using

%packages
...
sssd-client.i686
...
%end

will install

sssd.x86_64.rpm
sssd-client.i686.rpm

which prevents user logins.

So I'm suggesting to adding an explicit Require: sssd-client(%arch) to sssd.spec. This would make sure 1) user logins always work as expected on 64-bit 2) creating cross 32/64-bit kickstart snippets will come much easier (especially consider appliance/livecd cases where one can't depend on things like %pre as with Anaconda).

Version-Release number of selected component (if applicable):
RHEL 6.1
Comment 4 Kaushik Banerjee 2011-09-30 06:28:22 UTC 
1. On a x86_64 machine: yum install sssd sssd-client.i686

2. # rpm -qa | grep sssd
sssd-1.5.1-52.el6.x86_64
sssd-client-1.5.1-52.el6.x86_64
sssd-client-1.5.1-52.el6.i686


Verified in version:
# rpm -qi sssd | head
Name        : sssd                         Relocations: (not relocatable)
Version     : 1.5.1                             Vendor: Red Hat, Inc.
Release     : 52.el6                        Build Date: Tue 20 Sep 2011 11:41:03 AM EDT
Install Date: Fri 30 Sep 2011 02:17:59 AM EDT      Build Host: x86-010.build.bos.redhat.com
Group       : Applications/System           Source RPM: sssd-1.5.1-52.el6.src.rpm
Size        : 3550647                          License: GPLv3+
Signature   : (none)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon
Comment 5 Jakub Hrozek 2011-10-26 16:56:02 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: The sssd deamon package did not explicitly specify that it required sssd-client package of the same architecture
Consequence: It was difficult to specify to install both primary and secondary architecture sssd-client packages on multiarch systems.
Simply issuing "yum install sssd sssd-client.i686" on a x86_64 system would only install sssd-client.i686 while it should install both x86_64 and i686 systems
Fix: The main sssd package requires sssd-client of the same architecture
Result: Installing a secodary-arch sssd-client package would bring in the primary architecture sssd-client as well
Comment 6 errata-xmlrpc 2011-12-06 16:38:40 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.

http://rhn.redhat.com/errata/RHBA-2011-1529.html
Note You need to log in before you can comment on or make changes to this bug.