similar to: centos puppet user resource type - provider useradd does not support features manages_passwords

When I run puppet I see: "Provider useradd does not support features manages_passwords; not managing attribute password" [root@hostname local]# yum list installed | grep ruby-shadow ruby-shadow.x86_64 1.4.1-13.el6 @epel [root@hostname local]# ruby -rpuppet -e ''puts Puppet.features.libshadow?'' true [root@hostname local]#

hi, all Its a very common use-case to set common password for user/s on all nodes, i like to know if there is any Type or Function or Recipe available in puppet which support this case? I have tried following approach but it didn''t worked; I am reading the password (md5 hash) stored in a file called "/myuserpwd.file" Approach 1: ----------------- $password =

Hi, i would like to use the user provider on freebsd to manage passwords. This isn''t implemented at the moment as Luke said in Message-Id: <5FE94839-099E-43A6-A2A6-411224D9B531@madstop.com>. If you run pw with -h $fd or -H $fd you can provide a password via the file descriptor with nunber $fd (already encrypted in the latter case). I never read ruby till yesterday, but it looks

Both the server and the client in this example are running 2.6.5: One class seems to be causing the error: debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml /var/lib/gems/1.8/gems/puppet-2.6.5/lib/puppet/resource.rb:396:in

Hi list, i tried to write my first type and provider that should create logical volumes. Seems like i''m missing something as i get nothing when i use it: No errors and no logical volume :-( type/logicalvolume.rb: ================= Puppet::Type.newtype(:logicalvolume) do @doc = "Manage logical volumes" ensurable newparam(:lvname) do desc "The logcal

Hello, I get these message when i try to run puppet with augeas. Puppet Version are 2.6.1 on server and client. The ouput of the puppet Client with debug: debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Failed to load library ''shadow'' for feature ''libshadow'' debug:

Hi there, Have any of you Puppet users/abusers out there worked on or even succeeded at some sort of Continuous Integration of your Puppet-language codebase? I''m very interested to hear about the experiences of other people in the community on some of this stuff. If you were in Amsterdam for Puppet Camp you might have seen my talk on these kinds of things and I''m sure there are

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

Hi, is it possible to use the service resource type with a specific user ? So that the service is started with that given user instead of the puppet user starting it... Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/u6nkVpFJ_kcJ. To post

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

I am using Puppet 2.7.2 with ruby 1.8.7 (2010-01-10 patchlevel 249) and 64 bit Ubuntu 10.4. I have a Vagrant environment which I have been using for development. In the vagrant environment about 5 minutes is required to run all of the modules used for the configuration I have been developing. When I run exactly the same modules in AWS several hours are required. The Vagrant VM has 1 CPU and 1 GB

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

Hi all, I have been working on a configuration of a Masterless configuration on Windows. I am able to get individual jobs to run like: puppet apply <path to my puppet .pp file> However, I would like to spin up the Vagrant box off a base VM, and have a puppet manifest file in a location where puppet knows to look and provision based off that file. The obvious place seems to be

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi gluster ! For those of you who need to spin up virtual gluster clusters for development and testing: Just finished creating a vagrantized, fully automated, totally rebuildable and teardownable two node fedora 19 gluster setup and shared it on the forge! It uses fedora19 but since its all vagrant powered, you dont need to grab or download a distro or iso or anything, just clone the git repo,

Hello, I'm converting my mailbox from Maildir to mdbox.. The Maildir is from an 1.2 server. The new server is a virtual FreeBSD ZFS server. The conversion is not working, I'm getting either segfaults or the sync just quits with errors. I also did set with mmap_disable=yes. This didn't resolve the problem. How can I fix this? The same conversion on a virtual ubuntu 14.04 box works

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

I''m working to expand / develop on the zpool built-in type, but the zpool command is failing and Puppet''s returned stderr is not what I get if I copy/paste the command given by the debug output. # cat /etc/puppet/manifests/zpool_raidz2.pp zpool { ''tank'': ensure => present, raidz => [ ''d01 d02 d03 d04'', ''d05 d06