RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1253480 - ipa vault-add-owner does not fail when adding an existing owner
Summary: ipa vault-add-owner does not fail when adding an existing owner
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 19:22 UTC by Scott Poore
Modified: 2015-11-19 12:05 UTC (History)
3 users (show)

Fixed In Version: ipa-4.2.0-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 12:05:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2362 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2015-11-19 10:40:46 UTC

Description Scott Poore 2015-08-13 19:22:03 UTC 
Description of problem:

[root@master ~]# ipa vault-add vname
-------------------
Added vault "vname"
-------------------
  Vault name: vname
  Type: standard
  Owner users: admin
[root@master ~]# ipa vault-add-owner vname --users=vaultuser1
  Vault name: vname
  Type: standard
  Owner users: admin, vaultuser1
------------------------
Number of owners added 1
------------------------
[root@master ~]# ipa vault-add-owner vname --users=vaultuser1
  Vault name: vname
  Type: standard
  Owner users: admin, vaultuser1
------------------------
Number of owners added 0
------------------------


Version-Release number of selected component (if applicable):
ipa-server-4.2.0-4.el7.x86_64

How reproducible:
always


Steps to Reproduce:
1.  ipa-server-install
2.  ipa-kra-install
3.  kinit admin
4.  ipa vault-add vname
5.  ipa vault-add-owner vname --users=user1
6.  ipa vault-add-owner vname --users=user1

Actual results:
no error

Expected results:
I expected an error/warning like vault-add-member shows:

[root@master ~]# ipa vault-add-member vname --groups=vaultvaultgroup1
  Vault name: vname
  Type: standard
  Owner users: admin
  Member groups: vaultvaultgroup1
  Failed members:
    member user:
    member group: vaultvaultgroup1: This entry is already a member


Additional info:
Comment 1 Scott Poore 2015-08-13 19:23:42 UTC 
same for group

[root@master ~]# ipa vault-add-owner vname --groups=vaultgroup1
  Vault name: vname
  Type: standard
  Owner users: admin
  Owner groups: vaultgroup1
------------------------
Number of owners added 1
------------------------
[root@master ~]# ipa vault-add-owner vname --groups=vaultgroup1
  Vault name: vname
  Type: standard
  Owner users: admin
  Owner groups: vaultgroup1
------------------------
Number of owners added 0
------------------------
Comment 3 Scott Poore 2015-08-14 01:13:41 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5214
Comment 4 Petr Vobornik 2015-08-18 09:18:56 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/d2da0d89d194f198728b858800dfec447c5d9595
https://fedorahosted.org/freeipa/changeset/d9e9e5088fe3e093e3291a5e8877e8651645fc61
ipa-4-2:
https://fedorahosted.org/freeipa/changeset/649a1a7c65d5ba99183dd0437d9ab4f20fa05530
https://fedorahosted.org/freeipa/changeset/f66d7043dc2f35bdc7f7f3774ecbc12046b7feef
Comment 6 Scott Poore 2015-08-21 18:07:24 UTC 
Verified.

Version ::

ipa-server-4.2.0-5.el7.x86_64

Results ::

[root@master ~]# ipa user-add user1 --first=f --last=l
------------------
Added user "user1"
------------------
  User login: user1
  First name: f
  Last name: l
  Full name: f l
  Display name: f l
  Initials: fl
  Home directory: /home/user1
  GECOS: f l
  Login shell: /bin/sh
  Kerberos principal: user1
  Email address: user1
  UID: 744800004
  GID: 744800004
  Password: False
  Member of groups: ipausers
  Kerberos keys available: False
[root@master ~]# ipa vault-add vname
-------------------
Added vault "vname"
-------------------
  Vault name: vname
  Type: standard
  Owner users: admin
  Vault user: admin
[root@master ~]# ipa vault-add-owner vname --users=user1

  Vault name: vname
  Type: standard
  Owner users: admin, user1
  Vault user: admin
------------------------
Number of owners added 1
------------------------
[root@master ~]# 
[root@master ~]# ipa vault-add-owner vname --users=user1
  Vault name: vname
  Type: standard
  Owner users: admin, user1
  Vault user: admin
  Failed owners: 
    owner user: user1: This entry is already a member
    owner group: 
    owner service: 
------------------------
Number of owners added 0
------------------------
Comment 7 errata-xmlrpc 2015-11-19 12:05:28 UTC 
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-2015-2362.html
Note You need to log in before you can comment on or make changes to this bug.