Closed
Bug 1037860
Opened 10 years ago
Closed 7 years ago
slaveapi didn't restart for new passwords
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dustin, Unassigned)
References
Details
When the new passwords were added yesterday, slaveapi didn't restart properly. I thought Callek was going to take a look, but I think we interpreted "in 4-5 hours" differently. The upshot is that it's now filing bugs like bug 1037832 for perfectly functional hosts.
Comment 1•10 years ago
|
||
Sorry!, Got tied up with some personal stuff last night. Please "stop" it today so we can stop filing invalid bugs and I'll get to it tonight for sure. Sorry for the hassle
Flags: needinfo?(bugspam.Callek)
Comment 2•10 years ago
|
||
Ooooook, so first off, When I was heading out yesterday, literally ~ a minute or two before I was shutting down comp: [22:48:59] <dustin> Callek: can you look at why slaveapi failed to restart on slaveapi1? [22:48:59] <dustin> credentials.json looks good to me [22:48:59] <Callek> dustin: ummmm, I can't for at least hours (~4-5 hours) perhaps bhearsum or someone else can [22:48:59] <dustin> ok This left me thinking it was handled since I saw no bug and no e-mail/or other response that it wasn't. Which is why I didn't get to this. [My response in c#1 was placed before I could even look at IRC scrollback to cross check if other things were said that I didn't recall] ..... anyway, so there was a weird situation here as well, `root` was the user running slaveapi when I looked, with slaveapi.log owned by root as well. So I stopped the proc as root, then chown'ed the directory to cltbld. Then switched to cltbld and restarted it, things seem ok now, so I'm calling this good. If there is any issues here, please please email and/or SMS me. :dustin did you do/try anything with this host directly, after deploying the password changes?
Flags: needinfo?(bugspam.Callek) → needinfo?(dustin)
Updated•10 years ago
|
Assignee: nobody → bugspam.Callek
Reporter | ||
Comment 3•10 years ago
|
||
No - I just got a puppet error about failing to restart, and then pinged you. And, sorry for the miscommunication!
Updated•10 years ago
|
Flags: needinfo?(dustin)
Comment 5•8 years ago
|
||
I'm not working on this, but offhand I'm not sure how important this is..
Component: General Automation → Buildduty
QA Contact: catlee → bugspam.Callek
Updated•8 years ago
|
Assignee: bugspam.Callek → nobody
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•