thr3ads.net - Puppet users - [Puppet Users] troubles with require parametre [Feb 2011]

If this information is useful, please help other people find it:
Share via:

tortuegeniale

2011-Feb-15 15:43 UTC

[Puppet Users] troubles with require parametre

Hi all,

Getting some troubles installing bind:
I''m working on debian squeeze, both client and server are 2.6.2,
mod_passenger added.

in my class definition:
class conf_bind_nshost {
  include motd
  motd::register{"${name}": } #Register in motd
module

  package { "bind9":
    ensure => "1:9.7.2.dfsg.P3-1.1",
  }

  file {"dns":
    require => Package["bind9"],
    path => "/srv/dns",
    owner  => bind,
    group  => bind,
    mode   => 755,
    ensure => "directory"
  }

  $conf_files= ["named.conf", "named.conf.local",
"named.conf.options","hosted-zones.bdb.conf"]
  bind_file_dispatch { $conf_files: }

  service { "bind9":
    require => Package["bind9"],
    ensure => running,
    enable => true,
    pattern => "named",
    hasrestart => true,
    hasstatus => true,
    subscribe => [
      File["named.conf"],
      File["named.conf.local"],
      File["named.conf.options"],
      File["hosted-zones.bdb.conf"],
      ],
  }
}


The end of the debug output:
debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl
does not exist
debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update
does not exist
debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does
not exist
debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc
does not exist
debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not
exist
debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_info
does not exist
debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/
sbin/portupgrade does not exist
debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not
exist
debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper
does not exist
debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient
does not exist
debug: Puppet::Type::Package::ProviderYum: file yum does not exist
debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not
exist
debug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does
not exist
debug: Puppet::Type::Package::ProviderAix: file /usr/sbin/installp
does not exist
debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swlist does
not exist
debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/
portupgrade does not exist
debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-
nox does not exist
debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not
exist
debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_info does not
exist
debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge
does not exist
debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
debug: Puppet::Type::Package::ProviderGem: file gem does not exist
debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does
not exist
debug: Using cached certificate for ca
debug: Using cached certificate for myhost.mydomain.net
debug: Using cached certificate_revocation_list for ca
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
b64_zlib_yaml
/usr/lib/ruby/1.8/puppet/type/file/owner.rb:37:in `retrieve''
/usr/lib/ruby/1.8/puppet/type/file/owner.rb:32:in `collect''
/usr/lib/ruby/1.8/puppet/type/file/owner.rb:32:in `retrieve''
/usr/lib/ruby/1.8/puppet/type.rb:695:in `retrieve''
/usr/lib/ruby/1.8/puppet/type.rb:690:in `each''
/usr/lib/ruby/1.8/puppet/type.rb:690:in `retrieve''
/usr/lib/ruby/1.8/puppet/type/file.rb:634:in `retrieve''
/usr/lib/ruby/1.8/puppet/type.rb:703:in `retrieve_resource''
/usr/lib/ruby/1.8/puppet/type.rb:1861:in `to_trans''
/usr/lib/ruby/1.8/puppet/type/file.rb:701:in `to_trans''
/usr/lib/ruby/1.8/puppet/type.rb:1886:in `to_resource''
/usr/lib/ruby/1.8/puppet/type.rb:203:in `uniqueness_key''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:83:in `add_resource''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:72:in `each''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:72:in `add_resource''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:561:in `to_catalog''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:531:in `each''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:531:in `to_catalog''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:468:in `to_ral''
/usr/lib/ruby/1.8/puppet/configurer.rb:117:in `convert_catalog''
/usr/lib/ruby/1.8/puppet/configurer.rb:112:in `retrieve_catalog''
/usr/lib/ruby/1.8/puppet/configurer.rb:143:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize''
/usr/lib/ruby/1.8/puppet/agent.rb:39:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:103:in `with_client''
/usr/lib/ruby/1.8/puppet/agent.rb:37:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:171:in `call''
/usr/lib/ruby/1.8/puppet/application.rb:171:in `controlled_run''
/usr/lib/ruby/1.8/puppet/agent.rb:35:in `run''
/usr/lib/ruby/1.8/puppet/application/agent.rb:114:in `onetime''
/usr/lib/ruby/1.8/puppet/application/agent.rb:88:in `run_command''
/usr/lib/ruby/1.8/puppet/application.rb:287:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:393:in `exit_on_fail''
/usr/lib/ruby/1.8/puppet/application.rb:287:in `run''
/usr/sbin/puppetd:4
err: Could not run Puppet configuration client: Could not find user
bind


Beside this, the catalogue showing the right require, if i understand
correctly:
- &id165 !ruby/object:Puppet::Relationship
      source: *id017
      target: &id142 !ruby/object:Puppet::Resource
        catalog: *id001
        exported:
        file: *id018
        line: 91
        parameters:
          !ruby/sym group: bind
          !ruby/sym ensure: directory
          !ruby/sym owner: bind
          !ruby/sym require: !ruby/object:Puppet::Resource
            parameters: {}
            tags:
              - package
              - bind9
            title: bind9
            type: Package
          !ruby/sym path: /srv/dns
          !ruby/sym mode: "755"
        tags:
          - file
          - dns
          - class
          - conf_bind_nshost
          - nshost
        title: dns
        type: File
        virtual:


Does this sound familiar to someone?

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2011-Feb-15 16:53 UTC

head link

Re: [Puppet Users] troubles with require parametre

On Tue, Feb 15, 2011 at 7:43 AM, tortuegeniale
<o0o.atlantis.o0o@gmail.com> wrote:> Hi all,
>
> Getting some troubles installing bind:
> err: Could not run Puppet configuration client: Could not find user
> bind
It looks to me like you don''t have a User ''bind'' on
the target system,
and you haven''t defined one in the above manifest.

Does the bind package create a bind user for you?

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nicolas Szalay

2011-Feb-16 09:59 UTC

head link

Re: [Puppet Users] troubles with require parametre

Hello,

This case interests me :)

On Tue, Feb 15, 2011 at 5:53 PM, Nigel Kersten <nigel@puppetlabs.com>
wrote:
> It looks to me like you don''t have a User ''bind''
on the target system,
> and you haven''t defined one in the above manifest.
>
> Does the bind package create a bind user for you?

This looks like a bug. The bind package creates the "bind" user, but
the
File resource seems to prevent the Package resource realisation.

Is there a way to get the graph dependency when the run fails ?

Nico.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Christoph Maser

2011-Sep-20 10:54 UTC

head link

[Puppet Users] Re: troubles with require parametre

Hi

is there any news on this topic, did you find a workaround?

-- 
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/-/FZaXGxabmpcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Maybe Matching Threads

Search for more maybe matching threads

Puppet users - Feb 2011 - troubles with require parametre

[Puppet Users] troubles with require parametre

Re: [Puppet Users] troubles with require parametre

Re: [Puppet Users] troubles with require parametre

[Puppet Users] Re: troubles with require parametre

Maybe Matching Threads