Hi Pubudu,

We followed the latest guide given above, but we are getting an error at
step 9, building the docker image.
The log :

2.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2am_runtime/pattern-7/README.md HTTP/1.1"
200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] "GET
/hieradata/dev/wso2/hieradata/wso2is_prepacked/pattern-1/default.yaml
HTTP/1.1" 200 -
172.17.0.2 - - [30/Jun/2017 12:44:29] code 404, message File not found



*172.17.0.2 - - [30/Jun/2017 12:44:29] "GET /manifests/ HTTP/1.1" 404 -The
command '/bin/sh -c bash /usr/local/bin/image-config.sh' returned a
non-zero code: 8Docker image
wso2am-gateway-manager-kubernetes-pattern-3:2.1.0 created.*Build process
completed in 0 minutes and 12 seconds
Cleaning...


Although it says the image is created, when we try to list the images we
don't see it.
docker images
REPOSITORY                                          TAG
IMAGE ID            CREATED             SIZE
<none>                                              <none>
bb1fbd050e82        20 minutes ago      232MB
<none>                                              <none>
e115a82ab1c9        30 minutes ago      232MB
<none>                                              <none>
63f7208ec0ca        41 minutes ago      232MB
<none>                                              <none>
8d7232ae31d9        42 minutes ago      232MB
<none>                                              <none>
82d067d96a24        43 minutes ago      232MB
<none>                                              <none>
849952ec5cfc        44 minutes ago      232MB
<none>                                              <none>
f0940512761d        45 minutes ago      232MB
<none>                                              <none>
ce7f1779b174        45 minutes ago      232MB
<none>                                              <none>
f9011faab51b        45 minutes ago      232MB
<none>                                              <none>
6b2550bd75b4        45 minutes ago      232MB
<none>                                              <none>
9331674976a6        About an hour ago   232MB

I think  it fails to execute the image-config.sh due to some reason.
Any idea how to resolve this?

Thanks,
Dileepa

On Wed, Jun 28, 2017 at 11:01 PM, Dileepa Jayakody <
dileepajayak...@gmail.com> wrote:

> Hi Pubudu,
>
> Thank you very much for the pointer. We will try out the new kubernetes
> artifacts and get back to you with our findings.
>
> Regards,
> Dileepa
>
> On Wed, Jun 28, 2017 at 8:00 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi Dileepa,
>>
>> What you have followed is very old and we haven't tested those Kubernetes
>> artifacts with APIM 2.1.0. We are currently in the process of updating
>> Kubernetes artifacts for the APIM 2.1.0. You can find the latest artifacts
>> in [1]. Please follow this and let us know if you find any issues.
>>
>> The reason for the above behavior is that it keeps waiting for the
>> service to be active. Do you see any wso2am pods in the deployment?
>> Kubernetes data model has been changed and it is always better to try the
>> latest artifacts as we have tested some of the patterns with the new
>> deployment model [1].
>>
>> [1] - https://github.com/wso2/kubernetes-apim/tree/2.1.0
>>
>> Thank you!
>>
>> On Tue, Jun 27, 2017 at 7:00 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We have been following the kubernetes deployment guide for WSO2 products
>>> [1] to deploy APIM 2.1.0 in kubernetes on Google cloud. We have also
>>> followed the blog post [2] as a reference.
>>> When I execute the final deploy command by running
>>> $KUBERNETES_HOME/wso2am/deploy.sh it keeps on idling at message : *Waiting
>>> wso2am to launch on http://104.198.75.29:32003 <http://104.198.75.29:32003>*
>>>
>>> When we try to access above given URL, we get a connection time-out.
>>> Further we have also created firewall rules in GC to open ports :
>>> 9443,9763,8280,8243.
>>> But cannot access any of these endpoints, and can't access the carbon
>>> mgt console.
>>>
>>> Also in the kubernetes service deployed in GC we can't see any external
>>> endpoint exposed.
>>>
>>> Appreciate if someone can please give us any tip to resolve this and get
>>> the deployment working.
>>>
>>> Regards,
>>> Dileepa
>>>
>>>
>>> [1] https://docs.wso2.com/display/KA100/Deploying+and+Undeployin
>>> g+a+WSO2+Product+on+Kubernetes
>>> [2] http://rushmin.blogspot.com/2016/11/deploying-wso2-products-
>>> in-google.html
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to