Closed Bug 1256689 Opened 8 years ago Closed 6 years ago

puppetizing new aws masters requires manual intervention

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kmoir, Unassigned)

Details

bb-master130 and 131 were recently puppetized.  However, upon logging in they specified they need a reboot due to recent puppet changes.  I rebooted them but the same message appeared after reboot. I had to run puppet manually and reboot to remove to login message to reboot.  I think something is wrong with the order that things are installed on masters that are causing this problem.
see bug 1210629 for a similar problem
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Found in Triage: Since we don;t use BuildBot anymore, this bug should be closed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.