Bug 1236635
| Summary: | 389-admin TPS srpmtest failure | ||
|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Viktor Ashirov <vashirov> |
| Component: | Admin | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.1.1 | CC: | arubin, nhosoi, nkinder |
| Target Milestone: | DS10.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-admin-1.1.44-1.el7dsrv | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-07 15:39:00 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: | |||
|
Description
Viktor Ashirov
2015-06-29 15:31:36 UTC
Ah, I see. Thanks for narrowing down the issue, Viktor. Instead of *, we should have put *.conf or something more specific...
m4/mod_nss.m4
if test -z "$nsspcache" ; then
nsspcache=`grep NSSPassPhraseHelper $httpd_root/conf.d/* | awk '{print $2}'`
fi
These are twin sisters.
389-admin-1.1.42-1.el7dsrv nhosoi 2015-06-08 17:13:39 complete
389-admin-1.1.42-1.el6dsrv nhosoi 2015-06-08 17:12:00 complete
Was 389-admin-1.1.42-1.el7dsrv okay with the same code for RHDS 10?
Is this a test/release stopper?
(In reply to Noriko Hosoi from comment #1) > These are twin sisters. > 389-admin-1.1.42-1.el7dsrv nhosoi 2015-06-08 17:13:39 complete > 389-admin-1.1.42-1.el6dsrv nhosoi 2015-06-08 17:12:00 complete > > Was 389-admin-1.1.42-1.el7dsrv okay with the same code for RHDS 10? I don't remember that we had exact same issue, but only because we had other problems with TPS. And because of that we tested not on "stable" TPS systems, but on erratified beaker machines. But the code is the same and it can be triggered in unclean environment on RHDS10. > Is this a test/release stopper? No, this srpmtest failure is not not a test/release stopper. In clean environment where we build our packages (brew or mock) it's not reproducible. Moreover, rpms that are built by customers from srpms are not supported. So customers should not encounter this issue. Per triage,
> ACK. We should fix for 10.1.
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://rhn.redhat.com/errata/RHBA-2016-2665.html |