Thanks Lakmal, I'm now investigating the reason for the initial error which
was raised with Kubernetes v0.2-96.
Thanks
On Mon, Dec 22, 2014 at 11:45 PM, Lakmal Warusawithana <lak...@wso2.com>
wrote:
> My kubernetes setup used m2 is
>
> Kubernetes v0.2-96-gcc7999c00a40df
>
> On Mon, Dec 22, 2014 at 11:22 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> I tried the same flow with Kubernetes 0.5.2 and found a problem witih
>> Fannel:
>>
>> Dec 22 17:49:36 minion-1 systemd[1025]: Failed at step EXEC spawning
>> /opt/bin/flannel: No such file or directory
>> Dec 22 17:49:36 minion-1 systemd[1]: flannel.service: main process
>> exited, code=exited, status=203/EXEC
>> Dec 22 17:49:36 minion-1 systemd[1]: Unit flannel.service entered failed
>> state.
>> Dec 22 17:49:36 minion-1 systemd[1]: flannel.service failed.
>>
>> Thanks
>>
>> On Mon, Dec 22, 2014 at 8:26 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I see the below error in Kubernetes log after creating a service:
>>>
>>> Failed to find port for service: {{ http-9280 2014-12-22 14:11:02 +0000
>>> UTC 37836 } 4500 map[name:php.php.domain] map[name:php.php.domain] false
>>> {1 0 9280}}, no suitable port for manifest:
>>> 6220cc79-89e4-11e4-888f-080027c9178c
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
