Red Hat Bugzilla – Full Text Bug Listing
|Summary:||failure while writing changes to /etc/gshadow|
|Product:||[Fedora] Fedora||Reporter:||Stef Walter <stefw>|
|Component:||authconfig||Assignee:||Tomas Mraz <tmraz>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-02-17 09:22:55 EST||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Stef Walter 2012-08-03 02:45:30 EDT
Description of problem: When running authconfig to update the PAM configs, the following error message appears: [root@stef-rawhide ~]# /usr/sbin/authconfig --update --enablesssd --enablesssdauth grpconv: failure while writing changes to /etc/gshadow The pam_sss seems to work despite the above error. Version-Release number of selected component (if applicable): Installed Packages Name : authconfig Arch : x86_64 Version : 6.2.3 Release : 1.fc18 How reproducible: Every time. Steps to Reproduce: 1. Run command above. Actual results: Failure message. Expected results: No message, success.
Comment 1 Tomas Mraz 2012-08-06 05:58:16 EDT
Do you see any related AVC messages from SELinux? Use ausearch to find out. What does your /etc/gshadow file looks like? ls -Z /etc/gshadow
Comment 2 Stef Walter 2012-08-06 06:20:52 EDT
(In reply to comment #1) > Do you see any related AVC messages from SELinux? Use ausearch to find out. Is this the right syntax: # ausearch -f /etc/gpshadow <no matches> > What does your /etc/gshadow file looks like? ls -Z /etc/gshadow # ls -Z /etc/gshadow ----------. root root system_u:object_r:shadow_t:s0 /etc/gshadow
Comment 3 Tomas Mraz 2012-09-24 14:06:14 EDT
I've been now able to reproduce on fresh F18 Alpha install. I'll attach the avc log when I switch dontaudit off.
Comment 4 Tomas Mraz 2012-09-24 14:07:33 EDT
Created attachment 616682 [details] AVC messages logged
Comment 5 Tomas Mraz 2012-09-24 14:08:48 EDT
I think these read accesses to SELinux file contexts are legitimate and should be allowed by policy.
Comment 6 Fedora End Of Life 2013-04-03 13:53:41 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 7 Fedora End Of Life 2015-01-09 12:17:40 EST
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 8 Fedora End Of Life 2015-02-17 09:22:55 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.