Closed Bug 852147 Opened 12 years ago Closed 12 years ago

num_masters facter isn't set for the first master puppet run

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 803823

People

(Reporter: rail, Unassigned)

References

Details

(Whiteboard: [puppet])

I tried to puppetize a master in AWS and it failed with the following error: [10.134.49.182] out: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template buildmaster/buildbot.cfg.erb: [10.134.49.182] out: Filepath: /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb [10.134.49.182] out: Line: 65 [10.134.49.182] out: Detail: Could not find value for 'num_masters' at 5:/etc/puppet/production/modules/buildmaster/templates/buildbot.cfg.erb [10.134.49.182] out: at /etc/puppet/production/modules/buildmaster/manifests/init.pp:41 on node buildbot-master51.srv.releng.use1.mozilla.com [10.134.49.182] out: notice: Using cached catalog [10.134.49.182] out: err: Could not retrieve catalog; skipping run Looks like http://hg.mozilla.org/build/puppet/file/a5267cdc4944/modules/buildmaster/lib/facter/num_masters.rb#l4 doesn't set num_masters because ls: cannot access /etc/default/buildbot.d: No such file or directory
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.