Issue #1566: Crane returns 404 on /v1/_ping - Crane - Pulp

Actions

Send by e-mail Copy link

Issue #1566

closed

Crane returns 404 on /v1/_ping

Added by rbarlow over 8 years ago. Updated about 5 years ago.

Status:

CLOSED - NOTABUG

Priority:

Normal

Assignee:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version - Crane:

master

Platform Release:

Target Release - Crane:

OS:

Triaged:

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

I noticed today that Crane returns a 404 response on /v1/_ping:

(pulp)[vagrant@dev pulp]$ curl -I http://localhost:5000/v1/_ping
HTTP/1.1 404 Not Found
Content-Type: text/plain; charset=utf-8
Docker-Distribution-Api-Version: registry/2.0
X-Content-Type-Options: nosniff
Date: Thu, 21 Jan 2016 21:28:16 GMT
Content-Length: 19

I thought it was strange that it has the Docker v2 headers in the response, which might be a clue in fixing it. Here are the logs during that request:

172.17.0.1 - - [21/Jan/2016:21:28:16 +0000] "HEAD /v1/_ping HTTP/1.1" 404 19 "" "curl/7.43.0"

Actions

Copy link

Updated by mhrivnak over 8 years ago

Can't reproduce on master. In the vagrant environment, I did:

workon crane
python ./run.py

and in a different terminal:

curl -i http://127.0.0.1:5001/v1/_ping
HTTP/1.0 200 OK
Content-Type: application/json
Content-Length: 4
X-Docker-Registry-Standalone: True
X-Docker-Registry-Version: 0.6.6
X-Docker-Registry-Config: common
Server: Werkzeug/0.9.6 Python/2.7.10
Date: Fri, 22 Jan 2016 05:59:24 GMT

true

How are you running crane? I'm running it on a vagrant environment that hasn't been reprovisioned in a while.

Actions

Copy link