Network or some transient issue? Looks fine, now:
http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619 : { "id": "1s619"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619>, "type": "loadBalancerService"<http://84.39.51.47:8880/v2-beta/schemas/loadbalancerservice>, "links": { "self": "…/v2-beta/loadbalancerservices/1s619"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619>, "account": "…/v2-beta/loadbalancerservices/1s619/account"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/account>, "configItemStatuses": "…/v2-beta/loadbalancerservices/1s619/configitemstatuses"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/configitemstatuses>, "consumedbyservices": "…/v2-beta/loadbalancerservices/1s619/consumedbyservices"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/consumedbyservices>, "consumedservices": "…/v2-beta/loadbalancerservices/1s619/consumedservices"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/consumedservices>, "instances": "…/v2-beta/loadbalancerservices/1s619/instances"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/instances>, "networkDrivers": "…/v2-beta/loadbalancerservices/1s619/networkdrivers"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/networkdrivers>, "serviceExposeMaps": "…/v2-beta/loadbalancerservices/1s619/serviceexposemaps"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/serviceexposemaps>, "serviceLogs": "…/v2-beta/loadbalancerservices/1s619/servicelogs"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/servicelogs>, "stack": "…/v2-beta/loadbalancerservices/1s619/stack"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/stack>, "storageDrivers": "…/v2-beta/loadbalancerservices/1s619/storagedrivers"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/storagedrivers>, "containerStats": "…/v2-beta/loadbalancerservices/1s619/containerstats"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/containerstats> }, "actions": { "removeservicelink<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619>": "…/v2-beta/loadbalancerservices/1s619/?action=removeservicelink"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/?action=removeservicelink>, "addservicelink<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619>": "…/v2-beta/loadbalancerservices/1s619/?action=addservicelink"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/?action=addservicelink>, "setservicelinks<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619>": "…/v2-beta/loadbalancerservices/1s619/?action=setservicelinks"<http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619/?action=setservicelinks> }, "baseType": "service", "name": "lb-aa0a054b4460a11e89101027688d1e54", "state": "removed", "accountId": "1a7"<http://84.39.51.47:8880/v2-beta/accounts/1a7>, "assignServiceIpAddress": false, "created": "2018-04-22T08:53:29Z", "createdTS": 1524387209000, "currentScale": null, [etc...] -- Henry E. Thorpe 732-420-8735 [email protected] Platform & Systems Development D2 Architecture & Design AT&T Services, Inc. From: <[email protected]> on behalf of "[email protected]" <[email protected]> Date: Sunday, April 22, 2018 at 6:13 AM To: "[email protected]" <[email protected]> Subject: [onap-discuss] OOM K8S with DCAE Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 3m 3m 1 service-controller Warning CreatingLoadBalancerFailed Error creating load balancer (will retry): Failed to create load balancer for service onap-dcaegen2/dcaegen2: Error updating port rules for LB [lb-aa0a054b4460a11e89101027688d1e54]. Error: &client.ApiError{StatusCode:409, Url:"http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619";, Msg:"Bad response statusCode [409]. Status [409 Conflict]. Body: [code=Conflict, baseType=error, message=Conflict] from [http://84.39.51.47:8880/v2-beta/loadbalancerservices/1s619]";<https://urldefense.proofpoint.com/v2/url?u=http-3A__84.39.51.47-3A8880_v2-2Dbeta_loadbalancerservices_1s619-5D-2522&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=BvmpYbeQkmEyujUkKFUC-A&m=XSdV_8WZFlxJoD_mAuSTbjpbrsVZo6ZIvDz9zj5Gy5s&s=8IScn7fRreK7ZsXisvyDjgCgnbmlV38nJw2jmIhhjv0&e=>, Status:"409 Conflict", Body:"code=Conflict, baseType=error, message=Conflict"}. 2m 2m 1 service-controller Warning CreatingLoadBalancerFailed Error creating load balancer (will retry): Failed to create load balancer for service onap-dcaegen2/dcaegen2: Couldn't get publicEndpoints for LB lb-aa0a054b4460a11e89101027688d1e54 1m 1m 1 service-controller Warning CreatingLoadBalancerFailed Error creating load balancer (will retry): Failed to create load balancer for service onap-dcaegen2/dcaegen2: Couldn't call activate on LB lb-aa0a054b4460a11e89101027688d1e54 3m 42s 4 service-controller Normal CreatingLoadBalancer Creating load balancer
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
