Rudolf, 
 In your screencap I see tiller-deploy is "Running" but the  actual tiller 
container in in state: "Terminated" - it has restarted 143 times.
Check you cluster that the host VMs have registered using the correct routable 
IP back to the master
I would expect to see 0/1 in your get pods command

Check that tiller and your cluster is running OK by running the following
https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-VerifyyourKubernetesclusterisfunctioningproperly-Tillerisup

I also for openstack VM's usually need to override the derived/computed IP when 
running rancher (but not on AWS)
https://git.onap.org/logging-analytics/tree/deploy/aws/oom_cluster_host_install.sh#n43
 

An example of a running deployment
ubuntu@a-onap-devops:~$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    
RESTARTS   AGE
kube-system   heapster-6cfb49f776-9lqt2                  1/1       Running   0  
        20d
kube-system   kube-dns-75c8cb4ccb-tw992                  3/3       Running   0  
        20d
kube-system   kubernetes-dashboard-6f4c8b9cd5-rcbp2      1/1       Running   0  
        20d
kube-system   monitoring-grafana-76f5b489d5-r99rh        1/1       Running   0  
        20d
kube-system   monitoring-influxdb-6fc88bd58d-h875w       1/1       Running   0  
        20d
kube-system   tiller-deploy-645bd55c5d-bmxs7             1/1       Running   0  
        20d
onap          logdemonode-logdemonode-5c8bffb468-phbzd   2/2       Running   0  
        20d
onap          onap-log-elasticsearch-7557486bc4-72vpw    1/1       Running   0  
        20d
onap          onap-log-kibana-fc88b6b79-d88r7            1/1       Running   0  
        20d
onap          onap-log-logstash-9jlf2                    1/1       Running   0  
        20d
onap          onap-portal-app-8486dc7ff8-tssd2           2/2       Running   0  
        5d
onap          onap-portal-cassandra-8588fbd698-dksq5     1/1       Running   0  
        5d
onap          onap-portal-db-7d6b95cd94-66474            1/1       Running   0  
        5d
onap          onap-portal-sdk-77cd558c98-6rsvq           2/2       Running   0  
        5d
onap          onap-portal-widget-6469f4bc56-hms24        1/1       Running   0  
        5d
onap          onap-portal-zookeeper-5d8c598c4c-hck2d     1/1       Running   0  
        5d
onap          onap-robot-6f99cb989f-kpwdr                1/1       Running   0  
        20d
ubuntu@a-onap-devops:~$ kubectl describe pod tiller-deploy-645bd55c5d-bmxs7 -n 
kube-system
Name:           tiller-deploy-645bd55c5d-bmxs7
Namespace:      kube-system
Node:           a-onap-devops/172.17.0.1
Start Time:     Mon, 30 Jul 2018 22:20:09 +0000
Labels:         app=helm
                name=tiller
                pod-template-hash=2016811718
Annotations:    <none>
Status:         Running
IP:             10.42.0.5
Controlled By:  ReplicaSet/tiller-deploy-645bd55c5d
Containers:
  tiller:
    Container ID:  
docker://a26420061a01a5791401c2519974c3190bf9f53fce5a9157abe7890f1f08146a
    Image:         gcr.io/kubernetes-helm/tiller:v2.8.2
    Image ID:      
docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:9b373c71ea2dfdb7d42a6c6dada769cf93be682df7cfabb717748bdaef27d10a
    Port:          44134/TCP
    Command:
      /tiller
      --v=2
    State:          Running
      Started:      Mon, 30 Jul 2018 22:20:14 +0000
    Ready:          True

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of 
Rudolf Amirjanyan
Sent: Monday, August 20, 2018 1:28 AM
To: [email protected]; [email protected]
Subject: Re: [onap-discuss] Problem with helm (server version)

yes, its running.

 netstat -ntplu |grep 8879

tcp        0      0 127.0.0.1:8879          0.0.0.0:* LISTEN      11372/helm 

attaching screen shot of describe to see more details. --->

kubectl --namespace kube-system describe pod tiller-deploy-f44659b6c-px695

Thanks.



On 08/18/2018 05:07 PM, Joe Kidder wrote:
> Is tiller already running (and using port 8879)?
>
>> On Aug 18, 2018, at 7:53 AM, Rudolf Amirjanyan <[email protected]> wrote:
>>
>> Hello,
>>
>> Who can help me to understand why the tiller stops running at some point.
>>
>> When I run  --> helm serve &
>>
>>
>> root@myserver:/home/onaptest/oom/kubernetes# Regenerating index. This 
>> may take a moment.
>> Now serving you on 127.0.0.1:8879
>> Error: listen tcp 127.0.0.1:8879: bind: address already in use
>>
>> helm status -->
>> Error: could not find a ready tiller pod
>>
>>
>> regards,
>>
>> Rudolf
>>
>>
>> --
>>
>>
>>
>>
> 
>
>

-- 




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11961): https://lists.onap.org/g/onap-discuss/message/11961
Mute This Topic: https://lists.onap.org/mt/24666162/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to