Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2031825

Summary: Changing default pac type to 'nfs:NONE and MS-PAC' doesnot display error 'ipa: ERROR: no modifications to be performed'
Product: Red Hat Enterprise Linux 8 Reporter: Sudhir Menon <sumenon>
Component: ipaAssignee: Florence Blanc-Renaud <frenaud>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: frenaud, mvarun, rcritten, rjeffman, ssidhaye, tscherf
Target Milestone: rcKeywords: Regression
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: idm-DL1-8060020220203151553.92098735 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2040619 (view as bug list) Environment:
Last Closed: 2022-05-10 14:09:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2040619    

Description Sudhir Menon 2021-12-13 13:58:08 UTC
Description of problem: Changing default pac type to 'nfs:NONE and MS-PAC' doesnot display warning 'ipa: ERROR: no modifications to be performed'

Version-Release number of selected component (if applicable):
ipa-server-4.9.8-1.module+el8.6.0+13485+f71eb528.x86_64

How reproducible: Always


Steps to Reproduce:
1. ipa config-show
2. ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC

Actual results:
[root@server ~]# ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC
  Default PAC types: MS-PAC, nfs:NONE
[root@server ~]# echo $?
0

Expected results:
"ipa: ERROR: no modifications to be performed"


Additional info:

Comment 1 Florence Blanc-Renaud 2021-12-14 21:56:34 UTC
Easy to reproduce, and linked to the modifications related to Sid generation in ipa config-mod. I’ll work on a fix.

Comment 2 Florence Blanc-Renaud 2021-12-15 09:04:18 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/9063

Comment 11 Varun Mylaraiah 2022-02-23 18:01:49 UTC
Verified
ipa-server-4.9.8-6.module+el8.6.0+14224+4c38d4ea.x86_64

http://idm-artifacts.usersys.redhat.com/mvarun/trigger//3928/test-suite//restraint.01/index.html

2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] ::   Pac Type negative No Change
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] :: [ 12:45:16 ] :: [   LOG    ] :: negative:change pac type to it already is
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] :: [ 12:45:16 ] :: [  BEGIN   ] :: change default pac type to nfs:NONE and MS-PAC :: actually running 'ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC'
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] ipa: ERROR: no modifications to be performed
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] :: [ 12:45:17 ] :: [   PASS   ] :: change default pac type to nfs:NONE and MS-PAC (Expected 1, got 1)
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] :: [ 12:45:17 ] :: [  BEGIN   ] :: rechange default pac type to nfs:NONE and MS-PAC,verify the expected error message :: actually running 'verifyErrorMsg "ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC" "ipa: ERROR: no modifications to be performed"'
2022-02-23T17:45:17 [ip-10-0-195-88.rhos-] :: [ 12:45:17 ] :: [   LOG    ] :: Executing: ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC
2022-02-23T17:45:18 [ip-10-0-195-88.rhos-] ipa: ERROR: no modifications to be performed
2022-02-23T17:45:18 [ip-10-0-195-88.rhos-] :: [ 12:45:17 ] :: [   LOG    ] :: "ipa config-mod --pac-type=nfs:NONE --pac-type=MS-PAC" failed as expected.
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] :: [ 12:45:18 ] :: [   PASS   ] :: Error message as expected: ipa: ERROR: no modifications to be performed 
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] :: [ 12:45:18 ] :: [   PASS   ] :: rechange default pac type to nfs:NONE and MS-PAC,verify the expected error message (Expected 0, got 0)
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] ::   Duration: 2s
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] ::   Assertions: 3 good, 0 bad
2022-02-23T17:45:19 [ip-10-0-195-88.rhos-] ::   RESULT: PASS (Pac Type negative No Change)

Comment 14 errata-xmlrpc 2022-05-10 14:09:17 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 (idm:client and idm:DL1 bug fix and enhancement update), 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://access.redhat.com/errata/RHEA-2022:1884