sssd version in report is not in official rhel

sssd-common-1.16.1-0.20171114.1816.gitf6a1cef87.master.el7

Please provide steps to reproduce with version in rhel

it was caught with the above mentioned version, feel free to close if you think it's not valid.

(In reply to Vladimir Benes from comment #3)
> it was caught with the above mentioned version, feel free to close if you
> think it's not valid.

I am not against fixing crash even in git upstream version.

But Please provide steps to reproduce.
Backtrace is not enough for fixing the bug.
https://docs.pagure.org/SSSD.sssd/users/reporting_bugs.html

(In reply to Lukas Slebodnik from comment #4)
> (In reply to Vladimir Benes from comment #3)
> > it was caught with the above mentioned version, feel free to close if you
> > think it's not valid.
> 
> I am not against fixing crash even in git upstream version.
> 
> But Please provide steps to reproduce.
> Backtrace is not enough for fixing the bug.
> https://docs.pagure.org/SSSD.sssd/users/reporting_bugs.html

I have no steps to reproduce and sadly there is no more data attached. No additional data was found in FAF DB either. Feel free to close as insufficient info.

But actually it was triggered in your master branch so probably some jenkins CI job may carry some additional info.

(In reply to Vladimir Benes from comment #6)
> But actually it was triggered in your master branch so probably some jenkins
> CI job may carry some additional info.

Sorry for the lack of update on our side. Last Thursday we had a meeting and this bug was mentioned. Yes, it was indeed triggered by one of our jenkins CI job and Lukáš Slebodník is already investigating the issue (last week, even before this bug report, we briefly talked about the issue). It just took us some time to correlate the issue we've seen with this bug report.

Anyways, thanks for opening the bug!

Since the bug was needinfo'd since November and nobody cared enough to reply, I'm closing the bugzilla.

Looking at the backtrace here:
```
invoke_uusss_method() -> dp_get_account_info_handler() -> ... -> proxy_account_info_handler_send() -> save_group -> _talloc_steal_loc() -> raise
```
  --  I think this is the same as RHEL8 bz 1665867

This was fixed in sssd-2.x / RHEL8: https://bugzilla.redhat.com/show_bug.cgi?id=1665867#c9 and later required additional patch https://bugzilla.redhat.com/show_bug.cgi?id=1725168#c1

Since we do not have reproducer here, I can't be absolutely sure, of course.

But I think it makes sense to backport aforementioned patches to sssd-1-16/RHEL7 anyway.

Sumit, what would you say?

Hi Alexey,

thanks for spotting this. Yes, the backtraces indicate strongly that this might be the same issue. Unfortunately we do not have additional information, nevertheless I think it would be worth to backport the patches and add them to the next release if QE and PM agree.

bye,
Sumit

Upstream PR: https://github.com/SSSD/sssd/pull/1019

* `sssd-1-16`
    * e61f36189c4354a202f2b3bee86a026c7080690f - providers/proxy: fixed erroneous free of orig_grp
    * f6d20a58183d7a7ab20033a87ddd60798e809f80 - providers/proxy: got rid of excessive mem copies
    * 34412b2d90f324b178166af3ac852b4581f8493a - providers/proxy: fixed usage of wrong mem ctx
    * 80bfea505c45824f129290309c86e0df941914b7 - providers/proxy: fixed wrong check
    * 66b979b8d59a422dfbc7660016a09be44bc979f6 - providers/proxy: small optimization

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 (sssd bug fix and enhancement update), 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-2020:3904