Closed Bug 823033 Opened 12 years ago Closed 12 years ago

[Mozillians] Failed Chief Push

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P4)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: giorgos, Assigned: dmaher)

Details

(Whiteboard: [triaged 20121216])

Hello IT,

I pushed today to mozillians-stage and although everything looks to work as expected, Chief claims that the push was a failure.

Here is the link to chief logs: 

http://genericadm.private.phx1.mozilla.com/chief/mozillians.stage/logs/10f1939bc03.1355920054


Can you please investigate and explain what happened?

Thanks!
Assignee: server-ops-webops → dmaher
Status: NEW → ASSIGNED
Priority: -- → P4
Whiteboard: [triaged 20121216]
05:58:19 <@phrawzty> giorgos: the output looks normal enough, and if stage appears to have been deployed appropriately, then where's the problem ? :/
05:58:33 < giorgos> phrawzty, haha no worries
05:59:07 < giorgos> phrawzty, well no problem. I just had the chief bot complaining the something is wrong.
05:59:18 < giorgos> thnx for looking into it :)
06:03:56 < giorgos> phrawzty, I'll push some new code later this week and I'll re-open the bug if it doesn't clear. Sounds good?
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
the [err]ors you see in that log are the results of git returning stderr instead of stdout :( but don't worry, these aren't actually errors. thnx git :P
Chris,

Thanks for the answer. It's not the 'err's I'm referring to. We got these in other pushes (e.g.  http://genericadm.private.phx1.mozilla.com/chief/mozillians.stage/logs/15f595c.1354789568 ) and Chief didn't complain.

The last push displays as 'Failed' in the history, http://genericadm.private.phx1.mozilla.com/chief/mozillians.stage/history

and I don't understand why
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.