Hi All,
I am facing the same issue on deploying ONAP using Amsterdam release.
When I distribute my service in SDC, I am getting the same POL5000 error.
NOTE: AUTO.json contains external ip of host and not the internal ip of dmaap.
I am not deploying DCAE.
Can you please let me know if there is any workaround for this, or somehow we
can fix this.
Thanks and Regards,
Radhika
________________________________
From: onap-discuss-boun...@lists.onap.org <onap-discuss-boun...@lists.onap.org>
on behalf of Ptacek Michal <michal.pta...@tieto.com>
Sent: Tuesday, March 20, 2018 5:33:57 PM
To: abdelmuhaimen.sea...@orange.com; Ahmad, Munir; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB
cluster is not available"
Hi,
I had the same problem and patched it in AUTO.json in the same way.
This original IP is calculated from :
~/oom/kubernetes/config/docker/init/config-init.sh
kubectl get nodes -o jsonpath='{
$.items[*].status.addresses[?(@.type=="ExternalIP")].address }'
I think it need to be fixed in config-init container we need to have in
AUTO.json something like that:
…
"ueb_url_list":
"dmaap.onap-message-router,dmaap.onap-message-router",
...
"fqdn": ["dmaap.onap-message-router", "dmaap.onap-message-router"]
...
regards,
Michal
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of
abdelmuhaimen.sea...@orange.com
Sent: Sunday, March 18, 2018 9:56 PM
To: Ahmad, Munir <munir.ah...@bell.ca>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB
cluster is not available"
Here's the output showing now DE is UP after correcting IP Address.
root@olc-k8s:/dockerdata-nfs/onap/sdc/environments# curl -X GET
http://localhost:30205/sdc/v1/distributionUebCluster -H 'Accept:
application/json' -H 'Content-Type: application/json' -H
'X-ECOMP-InstanceID: mso' -H 'authorization: Basic
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU='
{"uebServerList":["10.43.205.37","10.43.205.37"]}
root@olc-k8s:/dockerdata-nfs/onap/sdc/environments# curl -X GET
http://localhost:30205/sdc2/rest/healthCheck
> ^C
root@olc-k8s:/dockerdata-nfs/onap/sdc/environments# curl -X GET
http://localhost:30205/sdc2/rest/healthCheck
{
"sdcVersion": "1.1.0",
"siteMode": "unknown",
"componentsInfo": [
{
"healthCheckComponent": "BE",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK"
},
{
"healthCheckComponent": "TITAN",
"healthCheckStatus": "UP",
"description": "OK"
},
{
"healthCheckComponent": "DE",
"healthCheckStatus": "UP",
"description": "OK"
},
{
"healthCheckComponent": "CASSANDRA",
"healthCheckStatus": "UP",
"description": "OK"
},
{
"healthCheckComponent": "ON_BOARDING",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK",
"componentsInfo": [
{
"healthCheckComponent": "ZU",
"healthCheckStatus": "UP",
"version": "0.2.0",
"description": "OK"
},
{
"healthCheckComponent": "BE",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK"
},
{
"healthCheckComponent": "CAS",
"healthCheckStatus": "UP",
"version": "2.1.17",
"description": "OK"
}
]
}
]
}
________________________________
From: SEAUDI Abdelmuhaimen OBS/CSO
Sent: Sunday, March 18, 2018 10:34 PM
To: Ahmad, Munir;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB
cluster is not available"
Hi Munir,
Thanks for your reply.
I found out that the reason SDC is using the external IP of DMAAP, instead of
the internal IP, is the configuration file
/dockerdata-nfs/onap/sdc/environments/AUTO.json, which mentions :
"ueb_url_list": "84.39.48.90,84.39.48.90"
Shouldn't SDC be configured with the K8S internal IP address of the DMAAP, for
example in my case it should be the IP Address 10.43.205.37 as per the output
from kubectl get services below ?
How can this be corrected ?
kubectl get services --all-namespaces
NAMESPACE NAME CLUSTER-IP EXTERNAL-IP
PORT(S) AGE
onap-message-router dmaap 10.43.205.37 <nodes>
3904:30227/TCP,3905:30226/TCP 24m
root@olc-k8s:~#
________________________________
From: Ahmad, Munir [munir.ah...@bell.ca]
Sent: Sunday, March 18, 2018 4:21 AM
To: SEAUDI Abdelmuhaimen OBS/CSO;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB
cluster is not available"
Hi,
It may have to do with the order your sdc containers started. Try deleting your
pods in the following order
sdc-es
sdc-cs
sdc-kb
sdc-be
sdc-fe
Thanks
Munir
From:
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
on behalf of
"abdelmuhaimen.sea...@orange.com<mailto:abdelmuhaimen.sea...@orange.com>"
<abdelmuhaimen.sea...@orange.com<mailto:abdelmuhaimen.sea...@orange.com>>
Date: Saturday, March 17, 2018 at 5:31 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>"
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] SDC distribution POL5000 error in K8S, "U-EB cluster is
not available"
Hi,
I have a minimal ONAP Depoloyment on K8S running.
If I try to distribute a new service in SDC, I get Error code POL5000, status
code: 500, Internal Server Error. Please try again later.
Regarding the output below, what does UEB Cluster not available mean ?
cloud@olc-k8s:~$ curl
http://127.0.0.1:30205/sdc2/rest/healthCheck<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2F127.0.0.1%3A30205%2Fsdc2%2Frest%2FhealthCheck&data=01%7C01%7Cradhika.kaslikar%40infosys.com%7C8192e19c306e4382cb1f08d58e5ae10c%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1&sdata=iIdiUeD3hsoHQUphhiB0YV4B9SfIWN%2F3bzn0h1fIJp4%3D&reserved=0>
{
"sdcVersion": "1.1.0",
"siteMode": "unknown",
"componentsInfo": [
{
"healthCheckComponent": "BE",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK"
},
{
"healthCheckComponent": "TITAN",
"healthCheckStatus": "UP",
"description": "OK"
},
{
"healthCheckComponent": "DE",
"healthCheckStatus": "DOWN",
"description": "U-EB cluster is not available"
},
{
"healthCheckComponent": "CASSANDRA",
"healthCheckStatus": "UP",
"description": "OK"
},
{
"healthCheckComponent": "ON_BOARDING",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK",
"componentsInfo": [
{
"healthCheckComponent": "ZU",
"healthCheckStatus": "UP",
"version": "0.2.0",
"description": "OK"
},
{
"healthCheckComponent": "BE",
"healthCheckStatus": "UP",
"version": "1.1.0",
"description": "OK"
},
{
"healthCheckComponent": "CAS",
"healthCheckStatus": "UP",
"version": "2.1.17",
"description": "OK"
}
]
}
]
}
cloud@olc-k8s:~$ curl -X GET
http://localhost:30205/sdc/v1/distributionUebCluster -H 'Accept:
application/json' -H 'Content-Type: application/json' -H
'X-ECOMP-InstanceID: mso' -H 'authorization: Basic
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU='
{"uebServerList":["X.Y.Z.90","X.Y.X.90"]} <<<<< i hide the ip address,
both are the same ip
cloud@olc-k8s:~$
cloud@olc-k8s:~$
root@olc-k8s:~/oom/kubernetes/oneclick# watch 'free -h;echo
===================; df -h /dev/vda1; df -h /dev/vdb1; echo
===================; kubectl get pods --all-namespaces'
Every 2.0s: free -h;echo ===================; df -h /dev/vda1; df -h /dev/vdb1;
echo ===================; kubectl get pods --all-namespaces
Sat Mar 17 09:30:32 2018
total used free shared buff/cache available
Mem: 61G 41G 1.8G 60M 18G 19G
Swap: 0B 0B 0B
===================
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 49G 7.4G 41G 16% /
Filesystem Size Used Avail Use% Mounted on
/dev/vdb1 197G 29G 159G 16% /var/lib/docker
===================
NAMESPACE NAME READY STATUS
RESTARTS AGE
kube-system heapster-4285517626-1q6rj 1/1 Running
0 23h
kube-system kube-dns-638003847-xb3mc 3/3 Running
0 23h
kube-system kubernetes-dashboard-716739405-s3tr3 1/1 Running
0 23h
kube-system monitoring-grafana-2360823841-15ppr 1/1 Running
0 23h
kube-system monitoring-influxdb-2323019309-3kvn2 1/1 Running
0 23h
kube-system tiller-deploy-737598192-4h8bj 1/1 Running
0 23h
onap-aai aai-resources-2398553481-pfnt0 2/2 Running
0 18h
onap-aai aai-service-749944520-cx9w5 1/1 Running
0 18h
onap-aai aai-traversal-2677319478-lccqd 2/2 Running
0 18h
onap-aai data-router-3700447603-3ftp1 1/1 Running
0 18h
onap-aai elasticsearch-622738319-zpwx2 1/1 Running
0 18h
onap-aai hbase-3471984843-zwxpj 1/1 Running
0 18h
onap-aai model-loader-service-911950978-5l2bk 2/2 Running
0 18h
onap-aai search-data-service-2471976899-rg1g9 2/2 Running
0 18h
onap-aai sparky-be-1779663793-td3m8 2/2 Running
0 18h
onap-message-router dmaap-3126594942-r3jg3 1/1 Running
0 18h
onap-message-router global-kafka-3848542622-14rbs 1/1 Running
0 18h
onap-message-router zookeeper-624700062-9zx7c 1/1 Running
0 18h
onap-mso mariadb-829081257-1jt7p 1/1 Running
0 53m
onap-mso mso-681186204-62xjj 2/2 Running
0 53m
onap-policy brmsgw-2284221413-mz4rr 1/1 Running
0 18h
onap-policy drools-534015681-zmkjn 2/2 Running
0 18h
onap-policy mariadb-559003789-dq74n 1/1 Running
0 18h
onap-policy nexus-687566637-99h5q 1/1 Running
0 18h
onap-policy pap-4181215123-thbr5 2/2 Running
0 18h
onap-policy pdp-2622241204-08mqw 2/2 Running
0 18h
onap-portal portalapps-1783099045-ncfkn 2/2 Running
0 18h
onap-portal portaldb-1451233177-72s9p 1/1 Running
0 18h
onap-portal portalwidgets-2060058548-73pm0 1/1 Running
0 18h
onap-portal vnc-portal-1252894321-39m9z 1/1 Running
0 18h
onap-sdc sdc-be-2336519847-02w8m 2/2 Running
0 18h
onap-sdc sdc-cs-1151560586-1q0zn 1/1 Running
0 18h
onap-sdc sdc-es-3319302712-3lrpv 1/1 Running
0 18h
onap-sdc sdc-fe-2862673798-9g2z1 2/2 Running
0 18h
onap-sdc sdc-kb-1258596734-c4h7v 1/1 Running
0 18h
onap-vid vid-mariadb-3318685446-jc1gl 1/1 Running
0 18h
onap-vid vid-server-421936131-cjhs2 2/2 Running
0 18h
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
