Comment 7 for bug 1390246

Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

Finally successful in deploying CoreOS template!

Here is the screen trace from the solum-deployer screen.

The resource was found at http://10.0.2.15:8004/v1/1cb3982d28cc480cbf72cfdfe90e5e6f/stacks/coreos3-nov11-df718e8a-14c3-4756-95d7-9e9cd2a8a4bd/f5a06c66-3d1d-4ecd-9ef9-d0e3a25c4e29; you should be redirected automatically.
 log_http_response /opt/stack/python-heatclient/heatclient/common/http.py:133
2014-11-11 17:42:58.222 1186 DEBUG heatclient.common.http [-] curl -i -X GET -H 'User-Agent: python-heatclient' -H 'Content-Type: application/json' -H 'X-Auth-Url: http://10.0.2.15:5000/v3' -H 'Accept: application/json' -H 'X-Auth-Token: {SHA1}80d9b287fbcfbaa59e771b156f5c7f1b9ee974ec' http://10.0.2.15:8004/v1/1cb3982d28cc480cbf72cfdfe90e5e6f/stacks/coreos3-nov11-df718e8a-14c3-4756-95d7-9e9cd2a8a4bd/f5a06c66-3d1d-4ecd-9ef9-d0e3a25c4e29 log_curl_request /opt/stack/python-heatclient/heatclient/common/http.py:120
2014-11-11 17:42:58.376 1186 DEBUG heatclient.common.http [-]
HTTP/1.1 200 OK
date: Tue, 11 Nov 2014 17:42:58 GMT
content-length: 1208
content-type: application/json; charset=UTF-8

{"stack": {"parent": null, "disable_rollback": true, "description": "Basic app deploy.\n", "links": [{"href": "http://10.0.2.15:8004/v1/1cb3982d28cc480cbf72cfdfe90e5e6f/stacks/coreos3-nov11-df718e8a-14c3-4756-95d7-9e9cd2a8a4bd/f5a06c66-3d1d-4ecd-9ef9-d0e3a25c4e29", "rel": "self"}], "stack_status_reason": "Stack CREATE completed successfully", "stack_name": "coreos3-nov11-df718e8a-14c3-4756-95d7-9e9cd2a8a4bd", "outputs": [{"output_value": "", "description": "The public IP address of the newly configured Server.", "output_key": "public_ip"}, {"output_value": "http://:5000", "description": "The URL for the Server.", "output_key": "URL"}], "stack_owner": null, "creation_time": "2014-11-11T17:42:47Z", "capabilities": [], "notification_topics": [], "updated_time": null, "timeout_mins": null, "stack_status": "CREATE_COMPLETE", "parameters": {"OS::stack_id": "f5a06c66-3d1d-4ecd-9ef9-d0e3a25c4e29", "OS::stack_name": "coreos3-nov11-df718e8a-14c3-4756-95d7-9e9cd2a8a4bd", "key_name": "", "image": "coreos", "du_image": "10.0.2.15:5042/nodeus", "flavor": "m1.small", "port": "5000", "app_name": "coreos3-nov11"}, "id": "f5a06c66-3d1d-4ecd-9ef9-d0e3a25c4e29", "template_description": "Basic app deploy.\n"}}
 log_http_response /opt/stack/python-heatclient/heatclient/common/http.py:133
2014-11-11 17:42:58.390 1186 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on 10.0.2.15:5672

solum assembly list shows the assembly to be in the 'READY' state.

However, it is not clear whether the container is actually up and running.

docker ps shows empty list (so, no container seems to have started up).

docker images shows following:

REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
10.0.2.15:5042/nodeus latest 798ba8b62ee4 6 minutes ago 855.7 MB

Notice that the "10.0.2.15:5042/nodeus" is same as the value of the "du_image" attribute passed to the heat template.

Some other observations.

1) The created container's image does seem to be getting uploaded to Glance. glance image-list does not show the 'nodeus' container in the list.

2) solum worker's handler does not seem to be creating/storing logs in /var/log/solum/worker/