Bug 1408678
| Summary: | [aaa-ldap-setup] Duplicate profile names definitions on availableProfiles | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine-extension-aaa-ldap | Reporter: | Gonza <grafuls> | ||||
| Component: | Setup | Assignee: | Ondra Machacek <omachace> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Gonza <grafuls> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | master | CC: | bugs, gklein, grafuls, mperina, oourfali, ylavi | ||||
| Target Milestone: | ovirt-4.1.1 | Keywords: | Reopened | ||||
| Target Release: | 1.3.1 | Flags: | rule-engine:
ovirt-4.1+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-extension-aaa-ldap-1.3.1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-04-21 09:31:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Strange, I can't reproduce. Did you see this issue only for RHDS with round-robin, or also for other providers or server sets? Only RHDS but I had this occur with single server too. Not able to reproduce it anymore neither. It still happens on this one server? (In reply to Oved Ourfali from comment #3) > It still happens on this one server? not anymore Found out the culprit for this issue. When running ovirt-engine-extension-aaa-ldap-setup with config file that contains rhds profile, the default baseDN is not correct. [environment:default] OVAAALDAP_LDAP/profile=str:rhds After further investigation, this is due to the profile name being invalid after the rhds profile names for both rhds and rhds rfc2307 being the same.
From log:
2017-02-09 14:34:03 DEBUG otopi.context context.dumpEnvironment:770 ENV OVAAALDAP_LDAP/availableProfiles=list:'[
...
{'profile': 'rfc2307-rhds', 'basedn': 'defaultNamingContext', 'display': 'RHDS RFC-2307 Schema'},
...
{'profile': 'rfc2307-rhds', 'basedn': 'defaultNamingContext', 'display': 'RHDS'}]'
Same issue with Oracle UD sharing profile name with openldap:
{'rfc2307-openldap', 'basedn': 'namingContexts', 'display': 'OpenLDAP RFC-2307 Schema'},
{'rfc2307-openldap', 'basedn': 'namingContexts', 'display': 'Oracle Unified Directory RFC-2307 Schema'},
(In reply to Gonza from comment #7) > Same issue with Oracle UD sharing profile name with openldap: > {'rfc2307-openldap', 'basedn': 'namingContexts', 'display': 'OpenLDAP > RFC-2307 Schema'}, > {'rfc2307-openldap', 'basedn': 'namingContexts', 'display': 'Oracle Unified > Directory RFC-2307 Schema'}, This is fine. Fix is present in ovirt-engine-extension-aaa-ldap-1.3.1 Verified with: ovirt-engine-extension-aaa-ldap-setup-1.3.1-1.el7ev.noarch |
Created attachment 1235350 [details] setup log Description of problem: Seems like default values for base DN are being taken from supportedLDAPVersion returned when performing search for base DN. Version-Release number of selected component (if applicable): ovirt-engine-extension-aaa-ldap-setup-1.3.1-0.0.master.20161219093217.git9a5d8da.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Run ovirt-engine-extension-aaa-ldap-setup and follow configuration for RHDS Actual results: Please enter base DN (2,3) [2]: Expected results: setup should show proper default values for base DN Additional info: ovirt-engine-extension-aaa-ldap-setup log attached