Bug 1558494

Summary: Rebase tevent to the latest available upstream release
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Hrozek <jhrozek>
Component: libteventAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: sssd-qe <sssd-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: asn, mupadhye, ovasik, sgoveas
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libtevent-0.9.36-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 07:56:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1558560    

Description Jakub Hrozek 2018-03-20 10:45:55 UTC
Description of problem:
This is needed to rebase Samba in 7.6

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Jakub Hrozek 2018-04-10 08:16:44 UTC
Hi Steeve,
can you qa_ack this bug? It's the same drill as every RHEL release, just testing the packages together with SSSD will make sure they work.

Comment 4 Madhuri 2018-08-10 10:31:48 UTC
Verified with
# rpm -qa sssd
sssd-1.16.2-11.el7.x86_64

# rpm -qa samba
samba-4.8.3-3.el7.x86_64

[root@ipaqavmh ~]# rpm -qa | grep samba
samba-common-libs-4.8.3-3.el7.x86_64
samba-libs-4.8.3-3.el7.x86_64
samba-common-4.8.3-3.el7.noarch
samba-common-tools-4.8.3-3.el7.x86_64
samba-client-libs-4.8.3-3.el7.x86_64
samba-4.8.3-3.el7.x86_64

[root@ipaqavmh ~]# rpm -qa | grep libtevent
libtevent-0.9.36-1.el7.x86_64

Installation and other sanity checks verifies current version of samba.

Thus on the basis of above observations, marking the status of bug to 'Verified'.

Comment 6 errata-xmlrpc 2018-10-30 07:56:47 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/RHEA-2018:3049