pki user-membership-add should add only existing users to the group
Steps to Reproduce:
# pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123 user-show u10 UserNotFoundException: User u10 not found # pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123 user-membership-add u10 Administrators ------------------------------------ Added membership in "Administrators" ------------------------------------ Group: Administrators # pki -d /opt/rhqa_pki/certs_db -n CA_adminV -c redhat123 group-member-find Administrators ----------------- 7 entries matched ----------------- User: caadmin User: CA_adminV User: CA_adminR User: CA_adminE User: CA_adminUTCA User: pkiUser1 User: u10
Actual results:
user-membership command adds a non-existing user to a group
Expected results:
user membership command should add only existing users to a group
Additional info:
Same behavior is seen with pki group-member-add Upstream ticket https://fedorahosted.org/pki/ticket/1024
Per CS/DS meeting of 06/15/2015: 10.3
Per Bug Triage of 05/03/2016: 10.4
Metadata Update from @mharmsen: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field component adjusted to Command-Line Utilities (was: CA) - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to 10.3 - Custom field proposedpriority adjusted to minor - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None
Metadata Update from @mharmsen: - Custom field lowhangingfruit adjusted to vakwetu: X - Issue priority set to: minor (was: major) - Issue set to the milestone: FUTURE (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
edewata: negative case
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1981
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.