Closed Bug 890517 Opened 11 years ago Closed 11 years ago

Error when pushing with Chief

Categories

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task, P2)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Engagement
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sgarrity, Assigned: dmaher)

Details

When logging into vpn.mozilla.com choosing "bedrock demo1" (or demo2 or demo3) under Web Bookmarks, I get the following error message:

 Cannot access the Web site. Please check your proxy settings. Made http request for GET /chief/bedrock.demo2 HTTP/1.1 to bedrockadm.private.phx1.mozilla.com:80. The URL you entered is incorrect or the Web site is not accessible. Administrator: Please make sure that the DNS Domain information is entered correctly. Made http request for GET /chief/bedrock.demo2 HTTP/1.1 to bedrockadm.private.phx1.mozilla.com:80.
I can confirm that all bedrock chief instances seem down; This includes staging and production instances.

Upping priority on this since it's now blocking our ability to push code to production.
Severity: normal → critical
Assignee: network-operations → ludovic
Component: Server Operations: Netops → Server Operations: Web Operations
QA Contact: ravi → nmaul
For some reason the HTTPd on bedrockadm was not running.  I've restarted it, and will add a Puppet rule to ensure that the service is running in the future.
Assignee: ludovic → dmaher
Status: NEW → RESOLVED
Closed: 11 years ago
Component: Server Operations: Web Operations → WebOps: Engagement
Priority: -- → P2
Product: mozilla.org → Infrastructure & Operations
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.