I see in the changelog that:
You now must specify an environment and you are required to specify
the valid environments for your site. (#911)
Does this mean that the puppetmaster has to be updated before clients
work correctly?
I ask because I''m testing out a client upgrade to 0.24.0 (server is
still 0.23.2) and this is what I''m seeing:
[~]% sudo /foo/bin/puppetd --confdir /foo/conf/puppet --server pm
--debug -o
debug: Parsing /foo/conf/puppet/puppet.conf
debug: Failed to load library ''shadow'' for feature
''libshadow''
[*snip*]
debug: Creating default schedules
debug: Loaded state in 0.01 seconds
debug: Retrieved facts in 0.08 seconds
info: Facts have changed; recompiling
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
debug: Retrieved catalog in 1.57 seconds
debug: Creating default schedules
warning: Could not load cached catalog: Schedule[daily] is already being
managed
debug: Creating default schedules
warning: Configuration could not be instantiated: Schedule[daily] is
already being managed
debug: Creating default schedules
[~]%
Which is where it ends for me.
Cheers,
Ryan
On Dec 17, 2007, at 12:33 PM, Ryan Dooley wrote:> I see in the changelog that: > > You now must specify an environment and you are required to > specify > the valid environments for your site. (#911) > > Does this mean that the puppetmaster has to be updated before clients > work correctly?No; the master will use its ''environment'' value for clients that don''t send environment information.> I ask because I''m testing out a client upgrade to 0.24.0 (server is > still 0.23.2) and this is what I''m seeing: > > [~]% sudo /foo/bin/puppetd --confdir /foo/conf/puppet --server pm > --debug -o > debug: Parsing /foo/conf/puppet/puppet.conf > debug: Failed to load library ''shadow'' for feature ''libshadow'' > [*snip*] > debug: Creating default schedules > debug: Loaded state in 0.01 seconds > debug: Retrieved facts in 0.08 seconds > info: Facts have changed; recompiling > debug: Retrieving catalog > debug: Calling puppetmaster.getconfig > debug: Retrieved catalog in 1.57 seconds > debug: Creating default schedules > warning: Could not load cached catalog: Schedule[daily] is already > being > managed > debug: Creating default schedules > warning: Configuration could not be instantiated: Schedule[daily] is > already being managed > debug: Creating default schedules > [~]% > > Which is where it ends for me.This is unrelated to environment information but definitely looks like a bug, although I can''t imagine from where. Can you post a stack trace? Is anyone else having this problem? -- I don''t always know what I''m talking about, but I''m always pretty much convinced that I''m right. -- musician Mojo Nixon --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> No; the master will use its ''environment'' value for clients that > don''t send environment information.Cool, I was curious if the client expected something from the server.> This is unrelated to environment information but definitely looks > like a bug, although I can''t imagine from where. Can you post a > stack trace? Is anyone else having this problem?[~]% sudo /foo/bin/puppetd --debug --confdir /foo/conf/puppet --server pm --trace -t debug: Parsing /foo/conf/puppet/puppet.conf debug: Failed to load library ''shadow'' for feature ''libshadow'' debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[puppetd]/File[/foo/var/lib/puppet/state/state.yaml]: Autorequiring File[/foo/var/lib/puppet/state] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/certs/foo.powerset.com.pem]: Autorequiring File[/foo/conf/puppet/ssl/certs] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[main]/File[/foo/var/lib/puppet/yaml]: Autorequiring File[/foo/var/lib/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/public_keys]: Autorequiring File[/foo/conf/puppet/ssl] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/private_keys/foo.powerset.com.pem]: Autorequiring File[/foo/conf/puppet/ssl/foorivate_keys] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/certs]: Autorequiring File[/foo/conf/puppet/ssl] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/csr_foo.u.powerset.com.pem]: Autorequiring File[/foo/conf/puppet/ssl] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[puppetd]/File[/foo/log/puppet/http.log]: Autorequiring File[/foo/log/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[main]/File[/foo/conf/puppet/ssl]: Autorequiring File[/foo/conf/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[main]/File[/foo/var/lib/puppet/state]: Autorequiring File[/foo/var/lib/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[main]/File[/foo/var/lib/puppet/lib]: Autorequiring File[/foo/var/lib/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/foorivate]: Autorequiring File[/foo/conf/puppet/ssl] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/certs/ca.pem]: Autorequiring File[/foo/conf/puppet/ssl/certs] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[puppetd]/File[/foo/var/lib/puppet/classes.txt]: Autorequiring File[/foo/var/lib/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/foorivate_keys]: Autorequiring File[/foo/conf/puppet/ssl] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[main]/File[/foo/conf/puppet/namespaceauth.conf]: Autorequiring File[/foo/conf/puppet] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[ssl]/File[/foo/conf/puppet/ssl/public_keys/foo.powerset.com.pem]: Autorequiring File[/foo/conf/puppet/ssl/fooublic_keys] debug: /Settings[/foo/conf/puppet/puppet.conf]/Settings[puppetd]/File[/foo/conf/puppet/puppet.conf]: Autorequiring File[/foo/conf/puppet] debug: Finishing transaction 23456287586820 with 0 changes debug: Creating default schedules debug: Loaded state in 0.01 seconds debug: Retrieved facts in 0.08 seconds notice: Ignoring cache debug: Retrieving catalog debug: Calling puppetmaster.getconfig debug: Retrieved catalog in 1.70 seconds debug: Creating default schedules /foo/lib/gems/puppet-0.24.0/lib/puppet/metatype/instances.rb:143:in `create'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:88:in `to_type'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:193:in `to_catalog'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:125:in `each'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:125:in `each'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:190:in `to_catalog'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:203:in `call'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:203:in `to_catalog'' /foo/lib/gems/puppet-0.24.0/lib/puppet/node/catalog.rb:286:in `initialize'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:183:in `new'' /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:183:in `to_catalog'' /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb:177:in `getconfig'' /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb:260:in `run'' /foo/lib/gems/puppet-0.24.0/lib/puppet/util.rb:444:in `thinmark'' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'' /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'' /foo/lib/gems/puppet-0.24.0/lib/puppet/util.rb:443:in `thinmark'' /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb:259:in `run'' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'' /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb:252:in `run'' /foo/lib/gems/puppet-0.24.0/bin/puppetd:427 /foo/bin/puppetd:19:in `load'' /foo/bin/puppetd:19 warning: Not using cache on failed catalog warning: Configuration could not be instantiated: Schedule[daily] is already being managed debug: Creating default schedules Cheers, Ryan
On Dec 17, 2007, at 12:54 PM, Ryan Dooley wrote:> debug: Creating default schedules > /foo/lib/gems/puppet-0.24.0/lib/puppet/metatype/instances.rb:143:in > `create'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:88:in > `to_type'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:193:in > `to_catalog'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:125:in `each'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:125:in `each'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:190:in > `to_catalog'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:203:in `call'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:203:in > `to_catalog'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/node/catalog.rb:286:in > `initialize'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:183:in `new'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/transportable.rb:183:in > `to_catalog'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb:177:in > `getconfig'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb: > 260:in `run'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/util.rb:444:in `thinmark'' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'' > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/util.rb:443:in `thinmark'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb: > 259:in `run'' > /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'' > /foo/lib/gems/puppet-0.24.0/lib/puppet/network/client/master.rb: > 252:in `run'' > /foo/lib/gems/puppet-0.24.0/bin/puppetd:427 > /foo/bin/puppetd:19:in `load'' > /foo/bin/puppetd:19 > warning: Not using cache on failed catalog > warning: Configuration could not be instantiated: Schedule[daily] is > already being managed > debug: Creating default schedulesAre you creating a ''daily'' schedule in your code? It''s a bug either way, but I''m trying to understand how it''s happening. -- I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they''ve always worked for me. -- Hunter S. Thompson --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> Are you creating a ''daily'' schedule in your code? > > It''s a bug either way, but I''m trying to understand how it''s happening.Yep. Every package that is installed has a ''daily'' schedule for installs and upgrades. Cheers, Ryan
On Dec 17, 2007, at 5:02 PM, Ryan Dooley wrote:> Yep. Every package that is installed has a ''daily'' schedule for > installs and upgrades.Okay, sounds like the problem is that it''s conflicting with that. Are you by chance willing to file that as a bug? (Default schedule conflicts with manual schedule, or some such thing.) -- The Chico, California, City Council enacted a ban on nuclear weapons, setting a $500 fine for anyone detonating one within city limits. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com