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 1378905 - Incorrect error code returned from krb5_child
Summary: Incorrect error code returned from krb5_child
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukas Slebodnik
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 13:28 UTC by Dan Lavu
Modified: 2020-05-04 10:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 09:37:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4231 0 None None None 2020-05-04 10:57:57 UTC

Description Dan Lavu 2016-09-23 13:28:39 UTC 
Description of problem:

It seems that the exit status has changed causing the following automated test that is used for regression testing to fail.

Test suite: ad parameters
Test Case: sss_ssh_knownhostsproxy001: bz 1071823 segfault when HostID back end target is not configured

NOTE, this is not a blocker, the user is still permitted to login, only the error code has changed. 

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Run ad_parameters test suite

Actual results:

:: [   PASS   ] :: Command 'ssh_user_password_login testuser01-1511559 Secret123' (Expected 0, got 0)
:: [   PASS   ] :: File '/var/log/messages' should not contain 'sssd_be\[[0-9]*\]: segfault' 
:: [   FAIL   ] :: File '/var/log/sssd/sssd_sssdad.com.log' should contain 'HostID back end target is not configured' 


Expected results:

:: [   PASS   ] :: Command 'ssh_user_password_login testuser01-1511559 Secret123' (Expected 0, got 0)
:: [   PASS   ] :: File '/var/log/messages' should not contain 'sssd_be\[[0-9]*\]: segfault' 
:: [   PASS   ] :: File '/var/log/sssd/sssd_sssdad.com.log' should contain 'HostID back end target is not configured' 


Additional info:

Previous patch that caused this bug.

https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org/thread/OM2BME5DKH3HBD23BB5SC73I5VTATIGD/#FFKZZXSHZXYIC3P6H3P4Z5INSPEZD6MC
Comment 1 Jakub Hrozek 2016-09-23 13:33:21 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3198
Comment 2 Jakub Hrozek 2016-09-23 13:34:36 UTC 
temporarily assigning to Lukas because he has some kind of a patch (even though it might need more work)
Comment 5 Lukas Slebodnik 2016-09-28 17:39:21 UTC 
(In reply to Dan Lavu from comment #0)
> Description of problem:
> 
> It seems that the exit status has changed causing the following automated
> test that is used for regression testing to fail.
> 
> Test suite: ad parameters
> Test Case: sss_ssh_knownhostsproxy001: bz 1071823 segfault when HostID back
> end target is not configured
> 
> NOTE, this is not a blocker, the user is still permitted to login, only the
> error code has changed. 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> Always
> 
> Steps to Reproduce:
> 1. Run ad_parameters test suite
> 
> Actual results:
> 
> :: [   PASS   ] :: Command 'ssh_user_password_login
> testuser01-1511559 Secret123' (Expected 0, got 0)
> :: [   PASS   ] :: File '/var/log/messages' should not contain
> 'sssd_be\[[0-9]*\]: segfault' 
> :: [   FAIL   ] :: File '/var/log/sssd/sssd_sssdad.com.log' should contain
> 'HostID back end target is not configured' 
> 
> 
> Expected results:
> 
> :: [   PASS   ] :: Command 'ssh_user_password_login
> testuser01-1511559 Secret123' (Expected 0, got 0)
> :: [   PASS   ] :: File '/var/log/messages' should not contain
> 'sssd_be\[[0-9]*\]: segfault' 
> :: [   PASS   ] :: File '/var/log/sssd/sssd_sssdad.com.log' should contain
> 'HostID back end target is not configured' 
> 
The error message was removed as part of data provider refactoring

https://git.fedorahosted.org/cgit/sssd.git/commit/?id=dea636af4d1902a081ee891f1b19ee2f8729d759
Comment 6 Jakub Hrozek 2016-09-29 07:55:08 UTC 
(In reply to Lukas Slebodnik from comment #5)
> The error message was removed as part of data provider refactoring
> 
> https://git.fedorahosted.org/cgit/sssd.git/commit/
> ?id=dea636af4d1902a081ee891f1b19ee2f8729d759

I think Dan linked a wrong test. This is about the confusion between locked and expired account.
Comment 7 Lukas Slebodnik 2016-10-14 09:37:15 UTC 
Than it would be better to one a new bug with correct description.
Comment 8 Dan Lavu 2016-10-17 13:13:18 UTC 
Sorry, I don't know where my head was that day, yes it was the wrong test. Here is the new ticket https://bugzilla.redhat.com/show_bug.cgi?id=1385665
Note You need to log in before you can comment on or make changes to this bug.