Description of problem: Using the puppet user module to change or set a users password in /etc/shadow does not work. Running puppet with --debug I see this: Provider useradd does not support features manages_passwords; not managing attribute password This message appears when ruby-shadow is not present. Yet I have ruby-shadow installed. F26's ruby-shadow-1.4.1-31.fc26.x86_64 is rather old and 'gem list' does not show ruby-shadow as an installed gem. I built the latest ruby-shadow 2.5.0 on my systems and this fixes the problem, so I suspect someone simply needs to build an updated ruby-shadow rpm. Version-Release number of selected component (if applicable): puppet-4.6.2-4.fc26.noarch ruby-shadow-1.4.1-31.fc26.x86_64 How reproducible: Very Steps to Reproduce: puppet apply -tv --execute "user {'bob': password => 'alice', }" grep bob /etc/shadow
Hit this issue as well - puppet in my case fails to load the existing library: Debug: Failed to load library 'shadow' for feature 'libshadow' Looking deeper, the whole library seems broken: # irb irb(main):001:0> require 'shadow' LoadError: /usr/lib64/ruby/vendor_ruby/shadow.so: undefined symbol: rb_iterator_p - /usr/lib64/ruby/vendor_ruby/shadow.so from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from (irb):1 from /usr/bin/irb:11:in `<main>' # dnf info ruby-shadow Installed Packages Name : ruby-shadow Version : 1.4.1 Release : 31.fc26 Arch : x86_64 Size : 21 k Source : ruby-shadow-1.4.1-31.fc26.src.rpm Repo : @System From repo : fedora Summary : Ruby bindings for shadow password access URL : http://ttsky.net/ License : Public Domain Description : Ruby bindings for shadow password access Is there an easy fix for this without having to bring in a non-standard library into the system?
Just ran into this too, upgrading from Fedora 24 to Fedora 26. For what it's worth, 1.4.1 looks extremely outdated: https://rubygems.org/gems/ruby-shadow and https://github.com/apalmblad/ruby-shadow/blob/master/HISTORY
Created attachment 1334744 [details] Patch to upgrade to 2.5.0 Update to 2.5.0, new upstream and some spec file cleanup.
Well, this is long overdue, but the way forward should be rubygem-shadow instead of ruby-shadow. Please see bug 782560
Ok, I see, request created: https://bugzilla.redhat.com/show_bug.cgi?id=1498991
Hi, new package rubygem-ruby-shadow is now in testing, if no negative feedback is received, rubygem-ruby-shadow will be pushed to Fedora 25, 26 and 27 and obsolete ruby-shadow.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. 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 26 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.