Bug 868853
Summary: | Winsync: DS error logs report wrong version of Windows AD when winsync is configured. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sankar Ramalingam <sramling> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | jgalipea, nhosoi, nkinder |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 389-ds-base-1.2.11.15-4.el6 | Doc Type: | Bug Fix |
Doc Text: |
Cause: When enabling replication level logging, winsync prints out what version of Windows/AD it detects. If it detects win2k3 or later, it prints out "detected win2k3 peer".
Consequence: This can be confusing if you are running a later version, such as win2k8
Fix: This patch changes the message to match this logic by printing "detected win2k3 or later peer".
Result: The version string is now less confusing and accurate.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 08:21:10 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: | 881827 |
Description
Sankar Ramalingam
2012-10-22 09:51:15 UTC
Note that the detection is really looking for win2k3 _or later_, so the error message should say "detected win2k3 or later peer". Upstream ticket: https://fedorahosted.org/389/ticket/503 This has been checked in upstream: master - e3357b44187acf3f43ad52a62c78911bea620b88 389-ds-base-1.2.11 - 98b809ba580530d9418e7bbf857e1ff2b79f75c8 Upgraded the existing 389-ds-base package for the existing winsync setup and observed that the error message is changed. windows_conn_connect : detected Win2k3 or later peer Hence marking the bug as Verified. 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. http://rhn.redhat.com/errata/RHSA-2013-0503.html |