Getting internal server error when running Dockerized dev environment

Bug #1400395 reported by Shaunak Kashyap
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
Fix Released
Low
Amit Gandhi

Bug Description

I have setup the Dockerized development environment by running "./dev up" from the "docker/fig/" directory. The Docker images are built just fine and containers are spun up just fine as well. When I try to make an API request, however, I get a 500 Internal Server Error response:

$ curl -v 'http://192.168.59.103:81/v1.0/services'
* About to connect() to 192.168.59.103 port 81 (#0)
* Trying 192.168.59.103...
* Adding handle: conn: 0x7f8c1a004400
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7f8c1a004400) send_pipe: 1, recv_pipe: 0
* Connected to 192.168.59.103 (192.168.59.103) port 81 (#0)
> GET /v1.0/services HTTP/1.1
> User-Agent: curl/7.30.0
> Host: 192.168.59.103:81
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Connection: close
< Content-Type: text/plain
<
* Closing connection 0
Internal Server Error

The docker log for the poppy dev container (poppydev_1) shows these error messages:

poppydev_1 | --- no python application found, check your startup logs for errors ---
poppydev_1 | [pid: 16|app: -1|req: -1/1] 192.168.59.3 () {36 vars in 670 bytes} [Mon Dec 8 11:58:51 2014] GET /v1.0/services => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)

I'm working off git commit sha d6d5b95f6f7c4a31c272281db475311b53638d57

description: updated
description: updated
Revision history for this message
Amit Gandhi (amit-gandhi) wrote :

I made a few changes to the Docker Fig setup in git commit ha 92b8e699422264348836a371474660191779d7b2 that may fix this issue.

Can you please try again. Be sure to read the updated Readme file as there are changes due to adding support for Rackspace Cloud DNS.

Let me know if you are still having issues.

Changed in poppy:
status: New → Incomplete
milestone: none → ongoing
Revision history for this message
Amit Gandhi (amit-gandhi) wrote :

hmm...,i suddenly seem to be getting this also.....digging in deeper as this was working earlier. May be a random sporadic issue.

Revision history for this message
Amit Gandhi (amit-gandhi) wrote :

what i noticed was if you docker-enter the container, and run poppy-server manually, you get an AuthenticationFailed: Incorrect/unauthorized credentials received error.

looking at the poppy.conf file that was copied into the container, it is missing all the environment variables that fig (and init.sh) should have populated.

looking into why it is not running init.sh...

Revision history for this message
Amit Gandhi (amit-gandhi) wrote :

running "fig -f docker/fig/fig_local.yml up -d" creates a working docker environment

however, running "tox -e apidocker" which recreates the dev docker environment for api test execution creates a faulty docker environment. Basically it hadn't been updated to use the new fig_local stuff.

I will update it.

Changed in poppy:
status: Incomplete → In Progress
assignee: nobody → Amit Gandhi (amit-gandhi)
milestone: ongoing → kilo-2
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to poppy (master)

Reviewed: https://review.openstack.org/141878
Committed: https://git.openstack.org/cgit/stackforge/poppy/commit/?id=b1252a71ecee5cacb9a32a10e077ec8db5d4040e
Submitter: Jenkins
Branch: master

commit b1252a71ecee5cacb9a32a10e077ec8db5d4040e
Author: amitgandhinz <email address hidden>
Date: Mon Dec 15 13:55:40 2014 -0500

    Fixed issue with running apidocker

    Change-Id: Icda1875d7352a28d53930a896909be07129abd66
    Closes-Bug: 1400395

Changed in poppy:
status: In Progress → Fix Committed
Changed in poppy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.