Bug 713481
| Summary: | Removed "RunAs External Group" is displayed in the output when "--all" switch is used. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Gowrishankar Rajaiyan <grajaiya> |
| Component: | ipa | Assignee: | Rob Crittenden <rcritten> |
| Status: | CLOSED ERRATA | QA Contact: | Chandrasekar Kannan <ckannan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | benl, dpal, jgalipea |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-2.1.0-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: When removing a runAsGroup value from a sudorule the command appears successful but the group is included in the output as still a member.
Consequence: The state of the entry is confusing.
Fix: Stale data was being returned to the user.
Result: The data is now refreshed before returning, showing the proper membership.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 18:33:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gowrishankar Rajaiyan
2011-06-15 14:18:38 UTC
master: 0359e2a0434c3c4e578a8d5fb3341084e82ada1c ipa-2-0: 42bf96df457c8c4a698d80fa7d1e4a60bb2fb4b6 [root@bumblebee ~]# ipa sudorule-show sudorule1 --all dn: ipauniqueid=7efc46e4-ff4f-11e0-a0a8-525400deab7b,cn=sudorules,cn=sudo,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com Rule name: sudorule1 Enabled: TRUE RunAs External Group: sudogrp1, sudogrp2, sudogrp3, sudogrp4, sudogrp5 RunAs Groups: grp1, grp2, grp3, grp4, grp5 ipauniqueid: 7efc46e4-ff4f-11e0-a0a8-525400deab7b objectclass: ipaassociation, ipasudorule [root@bumblebee ~]# [root@bumblebee ~]# ipa sudorule-remove-runasgroup sudorule1 --groups=sudogrp3 --all dn: ipauniqueid=7efc46e4-ff4f-11e0-a0a8-525400deab7b,cn=sudorules,cn=sudo,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com Rule name: sudorule1 Enabled: TRUE RunAs External Group: sudogrp1, sudogrp2, sudogrp4, sudogrp5 RunAs Groups: grp1, grp2, grp3, grp4, grp5 ipauniqueid: 7efc46e4-ff4f-11e0-a0a8-525400deab7b objectclass: ipaassociation, ipasudorule --------------------------- Number of members removed 1 --------------------------- [root@bumblebee ~]# Verified. Version: ipa-server-2.1.3-3.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: When removing a runAsGroup value from a sudorule the command appears successful but the group is included in the output as still a member.
Consequence: The state of the entry is confusing.
Fix: Stale data was being returned to the user.
Result: The data is now refreshed before returning, showing the proper membership.
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-2011-1533.html |