Bug 2099920 - Not able to change user password, even root fails with token manipulation error
Summary: Not able to change user password, even root fails with token manipulation error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: passwd
Version: 7.4
Hardware: All
OS: All
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Jiri Kucera
QA Contact: CS System Management SST QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-22 00:47 UTC by joel
Modified: 2023-06-30 08:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-30 08:02:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-125936 0 None None None 2022-06-22 01:02:39 UTC

Description joel 2022-06-22 00:47:40 UTC 
Description of problem:
We are not able to reset the passwords after rebooting the server via azure console (reset password).
It got failed while we tried to update the password.
Also we tried to recover the root password via hard reset of VM but it is giving below error:
Authentication token manipulation error.

RHEL 7.4 
No users can change password even in rescue mode
Comment 3 joel 2022-06-23 17:11:47 UTC 
Hello,

cu would like this to be expedited since it is severely impacting production environment.

Thanks
Comment 4 Jiri Kucera 2022-06-29 09:41:41 UTC 
It looks like that the error message comes from PAM. Iker, can you please verify?
Comment 5 Iker Pedrosa 2022-06-29 11:03:17 UTC 
Yes, that error message comes from PAM but I don't think the root cause lies in that package. I've been reviewing the complete customer case and there seems to be a problem when dealing with the password file (/etc/shadow), which causes PAM to be unable to modify the file and also to move it. For more information please check: https://access.redhat.com/support/cases/#/case/03203399/discussion?commentId=a0a6R00000SiqloQAB
Note You need to log in before you can comment on or make changes to this bug.