Bug 1370121 - 389-ds-base-1.3.4.0-29.el7_2 "hang" [NEEDINFO]
Summary: 389-ds-base-1.3.4.0-29.el7_2 "hang"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1329061
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 11:24 UTC by Marcel Kolaja
Modified: 2020-12-14 07:41 UTC (History)
15 users (show)

Fixed In Version: 389-ds-base-1.3.4.0-34.el7_2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1329061
Environment:
Last Closed: 2017-01-18 17:10:02 UTC
Target Upstream Version:
mkolaja: needinfo? (jreznik)


Attachments (Terms of Use)

Description Marcel Kolaja 2016-08-25 11:24:59 UTC
This bug has been copied from bug #1329061 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 4 mreynolds 2016-08-30 22:49:43 UTC
The brew build can be found here:

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=511561

Comment 5 Jason Spangler 2016-10-07 13:42:00 UTC
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=511561 does not seem accessible - is it a RedHat internal only URL?

Is there a way for people outside of RedHat to access the updated package yet?  I have a production system suffering 100% of the time from this bug and would like to test the fix.

Comment 6 mreynolds 2016-10-07 14:33:22 UTC
(In reply to Jason Spangler from comment #5)
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=511561 does
> not seem accessible - is it a RedHat internal only URL?
> 
> Is there a way for people outside of RedHat to access the updated package
> yet?  I have a production system suffering 100% of the time from this bug
> and would like to test the fix.

The "brew" build is internal.  This build was generated as a patch for a customer.  If you are a paying customer you can request this hotfix from the support team(GSS), or the only other option is to wait for RHEL 7.3 to be released (which should be soon, but I don't know the exact date).

Alternatively, you could test an upstream build on Fedora (23/24)

http://koji.fedoraproject.org/koji/buildinfo?buildID=789707

This is not the "exact" same build that will be used in 7.3, but for testing this fix, in a non-production env, it would be sufficient.


Note You need to log in before you can comment on or make changes to this bug.