Dear all, MSO fails HC (503 return code) is tracked under https://jira.onap.org/browse/MSO-13 The team has identified the issue with the docker container. The change has been submitted and is currently under testing.
Best regards Catherine From: onap-discuss-bounces at lists.onap.org [mailto:[email protected]] On Behalf Of PLATANIA, MARCO Sent: Monday, April 17, 2017 3:24 PM To: FREEMAN, BRIAN D <bf1936 at att.com>; Dhananjay Pavgi <DP00476350 at TechMahindra.com>; onap-discuss at lists.onap.org; Yang Xu (Yang, Fixed Network) <yang.xu3 at huawei.com> Subject: Re: [onap-discuss] MSO failure on vFW service instantiation ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi Brian, The model loader issue was on the A&AI side. Despite the 503 error message in MSO, all the containers are up and running. Unfortunately, rebooting the VM/containers didn?t help so far. We?ll have MSO team investigate. Thanks, Marco From: "FREEMAN, BRIAN D" <bf1936 at att.com<mailto:[email protected]>> Date: Saturday, April 15, 2017 at 7:03 AM To: Dhananjay Pavgi <DP00476350 at TechMahindra.com<mailto:DP00476350 at TechMahindra.com>>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>>, "Yang Xu (Yang, Fixed Network)" <yang.xu3 at huawei.com<mailto:yang.xu3 at huawei.com>> Subject: RE: [onap-discuss] MSO failure on vFW service instantiation Did you try restarting the MSO containers ? I think I remember a problem in release 1.0 that if SDC is slow in coming up the model loader in MSO takes an error path. BTW Healthcheck needs to pass before doing instantiation tests. We always run healthcheck before starting testing. Hope this helps. Brian From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Dhananjay Pavgi Sent: Saturday, April 15, 2017 2:14 AM To: PLATANIA, MARCO <platania at research.att.com<mailto:platania at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>; Yang Xu (Yang, Fixed Network) <yang.xu3 at huawei.com<mailto:yang.xu3 at huawei.com>> Subject: Re: [onap-discuss] MSO failure on vFW service instantiation Thanks, Marco. Wonder if fix is needed for this or there?s a workaround. i.e. in ONS Hackethelon, how was this tackeled when ONAP was brought up and demos were showcased? thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [id:image002.png at 01CE7323.F2727500] [NAP_logo_Sig] www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=_s8bmNweGbdoT48eBEdWbC0qLCfNjfxgzqeqsIMNmTQ&s=NPyfnrGdGBmqfE1Ezj9Jp8HYKTygG1jtNTbzCk2HMUk&e=> Platinum Member. Visit : http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=_s8bmNweGbdoT48eBEdWbC0qLCfNjfxgzqeqsIMNmTQ&s=S6gl6ScIHZWjr8bUjAbsoo6llC3Aa8eQIByEPBABOtw&e=> From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of PLATANIA, MARCO (MARCO) Sent: Saturday, April 15, 2017 6:55 AM To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>; Yang Xu (Yang, Fixed Network) <yang.xu3 at huawei.com<mailto:yang.xu3 at huawei.com>> Subject: Re: [onap-discuss] MSO failure on vFW service instantiation Hello Yang, We are aware of the issue with MSO. I opened a jira ticket about the 503 response to health check. MSO team will take care of it. Thanks, Marco On Fri, Apr 14, 2017 at 4:33 PM -0700, "Yang Xu (Yang, Fixed Network)" <Yang.Xu3 at huawei.com<mailto:Yang.Xu3 at huawei.com>> wrote: All, I installed ONAP release 1.0.0 on Rackspace today. I login robot-vm and run ?/opt/demo.sh init? first. Then when I use VID portal to instantiate vFW service, I get MSO failure message with ?Customer Global Id not found (404) in AAI, Global Subscriber id: Demonstration?. BTW, MSO also fails ?/opt/ete.sh health? test with 503. Anyone has an idea? Thanks, -Yang Response message on VID portal: 04/15/17 19:16:30 HTTP Status: OK (200) { "request": { "requestId": "152bdf95-c9fd-422b-b646-905e3a565ee4", "startTime": "Fri, 14 Apr 2017 23:16:20 GMT", "requestScope": "service", "requestType": "createInstance", "requestDetails": { "modelInfo": { "modelCustomizationName": null, "modelInvariantId": "fd938f9a-d9dc-4a03-be70-eee9e546b19c", "modelType": "service", "modelNameVersionId": "b05ea495-9923-4d46-beb3-192c36cbc764", "modelName": "tutorial service", "modelVersion": "1.0" }, "requestInfo": { "billingAccountNumber": null, "callbackUrl": null, "correlator": null, "orderNumber": null, "productFamilyId": null, "orderVersion": null, "source": "VID", "instanceName": "DemoInstance", "suppressRollback": false }, "relatedInstanceList": null, "subscriberInfo": { "globalSubscriberId": "Demonstration", "subscriberName": null }, "cloudConfiguration": null, "requestParameters": { "subscriptionServiceType": "vFW", "userParams": [] } }, "instanceReferences": { "serviceInstanceId": null, "serviceInstanceName": "DemoInstance", "vnfInstanceId": null, "vnfInstanceName": null, "vfModuleInstanceId": null, "vfModuleInstanceName": null, "volumeGroupInstanceId": null, "volumeGroupInstanceName": null, "networkInstanceId": null, "networkInstanceName": null }, "requestStatus": { "requestState": "FAILED", "statusMessage": " Customer Global Id not found (404) in AAI, Global Subscriber id: Demonstration", "percentProgress": 100, "finishTime": "Fri, 14 Apr 2017 23:16:20 GMT" } } } 04/15/17 19:16:20 HTTP Status: Accepted (202) { "requestReferences": { "instanceId": "339749c2-172b-49cf-af0e-a979efc89ecb", "requestId": "152bdf95-c9fd-422b-b646-905e3a565ee4" } } ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=_s8bmNweGbdoT48eBEdWbC0qLCfNjfxgzqeqsIMNmTQ&s=WIPchBTScYhFuGwIsevddO0mHMOXboRqe406-MEVgLg&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=_s8bmNweGbdoT48eBEdWbC0qLCfNjfxgzqeqsIMNmTQ&s=uNO8SIEQ4v61Ip4r-RJ9uHcodbsdH-qPoUnHE5rj2e8&e=> internally within TechMahindra. ============================================================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170419/7f84df90/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 13631 bytes Desc: image003.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170419/7f84df90/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 24421 bytes Desc: image004.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170419/7f84df90/attachment-0003.png>
