Closed Bug 564778 Opened 15 years ago Closed 14 years ago

Puppet didn't sync up slave before exiting on new talos slaves

Categories

(Release Engineering :: General, defect, P5)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [puppet])

Puppet is supposed to run, and block the Buildbot startup from happening, until it successfully syncs up with the master. This includes both waiting on the certificate and applying all of the manifests appropriate to it. This didn't happen for our latest batch of Talos rev3 slaves, which caused lots of issues when they started taking jobs.
Ben, what's the IT action?
Sorry, I misfiled this.
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
This is important, but realistically, doesn't bite us very often. Marking P5.
Priority: -- → P5
Whiteboard: [puppet]
I'll give you a (US) dollar if this wasn't the same thing as in bug 623816, or related - perhaps the refimage had the puppetdlock file in it? Given that there's no other data here, I think this could be dup'd to bug 623816, but I'll let you do so in case you know more.
Haven't seen this again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.