https://bugzilla.redhat.com/show_bug.cgi?id=846754 (Red Hat Enterprise Linux 6)
Description of problem: when do research of an existing rule with adding leading or trailing space on Automember page ,the rule still comes up as a search result While doing the same procedure on the user page ,the user won't come out. Search for existing user: # ipa user-find "dnsuser1" -------------- 1 user matched -------------- User login: dnsuser1 First name: dnsuser1 Last name: dnsuser1 Home directory: /home/dnsuser1 Login shell: /bin/sh UID: 1574000029 GID: 1574000029 Account disabled: False Password: True Kerberos keys available: True ---------------------------- Number of entries returned 1 ---------------------------- Searching with trailing space for user: # ipa user-find "dnsuser1 " --------------- 0 users matched --------------- ---------------------------- Number of entries returned 0 ---------------------------- Search for existing automember rule: # ipa automember-find "www" --type=group --------------- 1 rules matched --------------- Automember Rule: www ---------------------------- Number of entries returned 1 ---------------------------- Search for automember rule with trailing space # ipa automember-find "www " --type=group --------------- 1 rules matched --------------- Automember Rule: www ---------------------------- Number of entries returned 1 ---------------------------- Version-Release number of selected component (if applicable): freeipa-server-2.99.0-0.20120807T0818Zgitbe96146.fc17.x86_64 How reproducible: Always Steps to Reproduce: See description above Actual results: when do research of an existing rule with adding leading or trailing space on Automember page ,the rule still comes up as a search result Expected results: the rule not coming up. Additional info:
Metadata Update from @dpal: - Issue assigned to someone - Issue set to the milestone: Ticket Backlog
Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.