Not able to create Service Instance in VID

-1

I am using these env values to setup an ONAP instance on vanilla openstack.

artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0

For AAI, I ended up using docker version 1.1-STAGING-latest and gerrit branch master as I couldn't find artifact with above version in repo.

With this, when I try to create a firewall service instance in VID, I get this error -

"requestStatus": {
      "requestState": "FAILED",
      "statusMessage": " AAI Create Service Instance Failed, Error 404. Proposed new Create Instance Id was: 4184b883-aef6-448c-a177-f5d2fd65117e",
      "percentProgress": 100,
      "finishTime": "Wed, 25 Oct 2017 14:23:14 GMT"
    }

Appreciate any help on this issue !

Few observations :

Robot healthcheck and SDC's healthcheck looks ok except that Robot's one giving error for AAI due to certificate.
When service is distributed in SDC, I do see message on topic SDC-DISTR-NOTIF-TOPIC-AUTO with a Kafka consumer.
Service is added into MSO's catalog DB as well.
AAI model-loader error.log has errors like below. I think this is because distribution client is continuously attempting to connect but failing.

2017-10-25T12:26:17.257Z||Timer-0|ModelLoader||org.openecomp.sdc.impl.DistributionClientImpl||INFO|DistributionClient - init
2017-10-25T12:26:17.285Z||Timer-0|ModelLoader||org.openecomp.sdc.http.AsdcConnectorClient||ERROR|status from ASDC is org.openecomp.sdc.http.HttpAsdcResponse@1fc2252b
2017-10-25T12:26:17.285Z||Timer-0|ModelLoader||org.openecomp.sdc.http.AsdcConnectorClient||ERROR|DistributionClientResultImpl [responseStatus=ASDC_NOT_FOUND, responseMessage=ASDC not found]
2017-10-25T12:26:17.286Z||Timer-0|ModelLoader||org.onap.aai.modelloader.service.SdcConnectionJob||ERROR|MDLSVC2001E|MDLSVC2001E Unable to register with ASDC: Failed to initialize distribution client: ASDC not found|

Comment

CommentAdd your comment...

5 answers

1
0
-1
Michael Lando
May 06, 2018
for reference in the future please use this: https://wiki.onap.org/display/DW/SDC+Troubleshooting

503 usually means a configuration issue.
Comment
CommentAdd your comment...

-1

Hi Kedar,

You need to edit your "AUTO.json". You don't have IP address from this file.

"default_attributes": {
"CS_VIP": "172.17.0.3",
"BE_VIP": "172.17.0.5",
"FE_VIP": "172.17.0.6",
"KBN_VIP": "172.17.0.4",
"ES_VIP": "172.17.0.2",
"interfaces": {
"application": "eth0",
"private": "eth1"
},
"ECompP": {
"ecomp_rest_url": "http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/auxapi",
"ueb_url_list": "10.0.11.1,10.0.11.1",
"app_secret": "XftIATw9Jr3VzAcPqt3NnJOu", 
"app_key": "x9UfO7JsDn8BESVX", 
"inbox_name": "ECOMP-PORTAL-INBOX", 
"ecomp_redirect_url": "http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm", 
"app_topic_name": "ECOMP-PORTAL-OUTBOX-SDC1",
"decryption_key": "AGLDdG4D04BKm2IxIWEr8o=="
}, 
"UEB": {
"PublicKey": "iPIxkpAMI8qTcQj8",
"SecretKey": "Ehq3WyT4bkif4zwgEbvshGal",
"fqdn": ["10.0.11.1", "10.0.11.1"]
},
"Nodes": {
"CS": "172.17.0.3",
"BE": "172.17.0.5",
"FE": "172.17.0.6",
"KBN": "172.17.0.4",
"ES": "172.17.0.2"
}
},

Best regards

Comment

CommentAdd your comment...

1
0
-1
Kedar Ambekar
Nov 07, 2017
This helped me to get SDC 1.1 dockers pass health check.
stop all the dockers.
delete the Cassandra data rm -rf /data/CS/*
restart the Dockers.

Also, AAI to SDC communication looks ok now with 1.1 dockers on both sides.
Comment
CommentAdd your comment...
1
0
-1
Kedar Ambekar
Nov 07, 2017
For 1.1 dockers, SDC docker_health.sh gives below output. I see emails on mailing list reporting same error before but couldn't find solution.
Appreciate help from SDC team here..
{
"cluster_name" : "SDC-ES-AUTO",
"status" : "green",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"active_primary_shards" : 3,
"active_shards" : 3,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 0,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 100.0
}
BE health-Check:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 503 </title>
</head>
<body>
<h2>HTTP ERROR: 503</h2>
<p>Problem accessing /sdc2/rest/healthCheck. Reason:
<pre> Service Unavailable</pre></p>
<hr /><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.3.21.v20170918</a><hr/>
</body>
</html>

FE health-Check:
{
"sdcVersion": "UNKNOWN",
"siteMode": "UNKNOWN",
"componentsInfo": [
{
"healthCheckComponent": "FE",
"healthCheckStatus": "UP",
"version": "1.1.0-SNAPSHOT",
"description": "OK"
},
{
"healthCheckComponent": "BE",
"healthCheckStatus": "DOWN"
},
{
"healthCheckComponent": "TITAN",
"healthCheckStatus": "UNKNOWN"
},
{
"healthCheckComponent": "CASSANDRA",
"healthCheckStatus": "UNKNOWN"
},
{
"healthCheckComponent": "DE",
"healthCheckStatus": "UNKNOWN"
},
{
"healthCheckComponent": "ON_BOARDING",
"healthCheckStatus": "UNKNOWN"
}
]
}
Error [12] while user existance check
Comment
CommentAdd your comment...
1
0
-1
Kedar Ambekar
Nov 07, 2017
I think -
AAI 1.1 tries to use URL https://c2.vm1.sdc.simpledemo.openecomp.org:8443/sdc/v1/distributionUebCluster
SDC 1.0 has URL https://c2.vm1.sdc.simpledemo.openecomp.org:8443/asdc/v1/distributionUebCluster
I did try with SDC 1.1 dockers, but docker_health.sh shows these errors. I am trying again with updated SDC 1.1 dockers.
"healthCheckStatus": "UNKNOWN"

<h2>HTTP ERROR: 503</h2>
<p>Problem accessing /sdc2/rest/healthCheck. Reason:
<pre> Service Unavailable</pre></p>
Comment
CommentAdd your comment...