Hi, I was able to resolve the loadbalancer issue, actually it was related to an old OOM instance that did not completely remove the old LoadBalancer in Rancher, and the old Loadbalancer prevented the new OOM from activiating a new Loadbalancer.
I removed the old Loadbalancer in Rancher, and the new OOM dcagen2 service loadbalancer activated OK. More info on Loadbalancer from Rancher here: https://rancher.com/docs/rancher/latest/en/cattle/adding-load-balancers/ root@olc-k8s:~# kubectl describe service dcaegen2 --namespace onap-dcaegen2 Name: dcaegen2 Namespace: onap-dcaegen2 Labels: app=nginx Annotations: <none> Selector: app=nginx Type: LoadBalancer IP: 10.43.173.228 LoadBalancer Ingress: 84.39.51.47, 84.39.51.47, 84.39.51.47, 84.39.51.47, 84.39.51.47, 84.39.51.47 Port: aai-service 8443/TCP NodePort: aai-service 30600/TCP Endpoints: 10.42.146.225:8443 Port: dmaap 3904/TCP NodePort: dmaap 30601/TCP Endpoints: 10.42.146.225:3904 Port: sdc-be 8443/TCP NodePort: sdc-be 30602/TCP Endpoints: 10.42.146.225:8443 Port: pdp 8081/TCP NodePort: pdp 30603/TCP Endpoints: 10.42.146.225:8081 Port: msbapigw 80/TCP NodePort: msbapigw 30604/TCP Endpoints: 10.42.146.225:80 Port: multicloud-tinanium 9005/TCP NodePort: multicloud-tinanium 30605/TCP Endpoints: 10.42.146.225:9005 Session Affinity: None Events: <none> root@olc-k8s:~# ________________________________ From: SEAUDI Abdelmuhaimen OBS/CSO Sent: Monday, April 23, 2018 10:38 AM To: [email protected] Subject: RE: OOM K8S with DCAE Hi, After going through this: https://docs.openstack.org/magnum/ocata/dev/kubernetes-load-balancer.html It seems that K8S Loadbalancer should interface with Openstack (my current cloud) LBaaS service, to complete the creation of the Loadbalancer, so that’s why it cannot allocate public endpoints and cannot activate the Loadbalancer for nginx container. However, I noticed that if I call the nginex exposed ports, the services respond, so I am trying to get past this point. Now, I am receiving the following error when DCAE bootstrap VM tries to register with MultiCloud, I see that the dcae_vm_int.sh script could not get the correct token from MultiCloud. ===> Waiting for MultiCloud to get ready for getting 200 from http://vm1.openo.VyK5.simpledemo.onap.org:9005/api/multicloud-titanium_cloud/v0/swagger.json @ Mon Apr 23 07:03:22 UTC 2018 RESP CODE 200, matches with expected RESP CODE 200. ===> MultiCloud ready @ Mon Apr 23 07:03:22 UTC 2018 ===> Register DNS zone VyK5.dcaeg2.onap.org. under admin =====> Getting token from http://vm1.openo.VyK5.simpledemo.onap.org/api/multicloud-titanium_cloud/v0/pod25_fr1/identity/v3/auth/tokens Received Keystone token tmp_auth_token},</pre></li> from http://vm1.openo.VyK5.simpledemo.onap.org/api/multicloud-titanium_cloud/v0/pod25_fr1/identity/v3/auth/tokens * Trying 84.39.51.47... * Connected to vm1.openo.VyK5.simpledemo.onap.org (84.39.51.47) port 80 (#0) > GET > /api/multicloud-titanium_cloud/v0/pod25_fr1/dns-delegate/v2/zones?name=VyK5.dcaeg2.onap.org. > HTTP/1.1 > Host: vm1.openo.VyK5.simpledemo.onap.org > User-Agent: curl/7.47.0 > Accept: */* > Content-Type: application/json > X-Auth-Token: tmp_auth_token},</pre></li> > < HTTP/1.1 403 Forbidden < Server: nginx/1.12.2 < Date: Mon, 23 Apr 2018 07:03:22 GMT < Content-Type: application/json < Transfer-Encoding: chunked < Connection: keep-alive < Vary: Cookie < X-Frame-Options: SAMEORIGIN < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS < { [69 bytes data] * Connection #0 to host vm1.openo.VyK5.simpledemo.onap.org left intact =====> No zone of same name VyK5.dcaeg2.onap.org. found, creating new zone * Trying 84.39.51.47... * Connected to vm1.openo.VyK5.simpledemo.onap.org (84.39.51.47) port 80 (#0) > POST /api/multicloud-titanium_cloud/v0/pod25_fr1/dns-delegate/v2/zones > HTTP/1.1 > Host: vm1.openo.VyK5.simpledemo.onap.org > User-Agent: curl/7.47.0 > Accept: */* > Content-Type: application/json > X-Auth-Token: tmp_auth_token},</pre></li> > Content-Length: 67 > * upload completely sent off: 67 out of 67 bytes < HTTP/1.1 403 Forbidden < Server: nginx/1.12.2 < Date: Mon, 23 Apr 2018 07:03:22 GMT < Content-Type: application/json < Transfer-Encoding: chunked < Connection: keep-alive < Vary: Cookie < X-Frame-Options: SAMEORIGIN < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS < * Connection #0 to host vm1.openo.VyK5.simpledemo.onap.org left intact {"detail":"Authentication credentials were not provided."}=====> Zone listing * Trying 84.39.51.47... * Connected to vm1.openo.VyK5.simpledemo.onap.org (84.39.51.47) port 80 (#0) > GET /api/multicloud-titanium_cloud/v0/pod25_fr1/dns-delegate/v2/zones HTTP/1.1 > Host: vm1.openo.VyK5.simpledemo.onap.org > User-Agent: curl/7.47.0 > Accept: */* > Content-Type: application/json > X-Auth-Token: tmp_auth_token},</pre></li> > < HTTP/1.1 403 Forbidden < Server: nginx/1.12.2 < Date: Mon, 23 Apr 2018 07:03:22 GMT < Content-Type: application/json < Transfer-Encoding: chunked < Connection: keep-alive < Vary: Cookie < X-Frame-Options: SAMEORIGIN < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS < { [69 bytes data] * Connection #0 to host vm1.openo.VyK5.simpledemo.onap.org left intact { "detail": "Authentication credentials were not provided." } * Could not resolve host: Content-Type * Closing connection 0 * Trying 84.39.51.47... * Connected to vm1.openo.VyK5.simpledemo.onap.org (84.39.51.47) port 80 (#1) > GET > /api/multicloud-titanium_cloud/v0/pod25_fr1/dns-delegate/v2/zones?name=VyK5.dcaeg2.onap.org. > HTTP/1.1 > Host: vm1.openo.VyK5.simpledemo.onap.org > User-Agent: curl/7.47.0 > Accept: */* > X-Auth-Token: tmp_auth_token},</pre></li> > < HTTP/1.1 403 Forbidden < Server: nginx/1.12.2 < Date: Mon, 23 Apr 2018 07:03:23 GMT < Content-Type: application/json < Transfer-Encoding: chunked < Connection: keep-alive < Vary: Cookie < X-Frame-Options: SAMEORIGIN < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS < { [69 bytes data] * Connection #1 to host vm1.openo.VyK5.simpledemo.onap.org left intact =====> After creation, zone VyK5.dcaeg2.onap.org. ID is {"detail":"Authentication credentials were not provided."} Registration and configuration for proxying DNSaaS completed. Abdelmuhaimen Seaudi Orange Labs Egypt Email: [email protected]<mailto:[email protected]> Mobile: +2012 84644 733 From: SEAUDI Abdelmuhaimen OBS/CSO Sent: Sunday, April 22, 2018 11:03 AM To: [email protected] Subject: OOM K8S with DCAE Hi, I have an OOM Amsterdam K8S instance up running, but can’t get DCAE to run, I get the following error. Any clue what is wrong here ? root@olc-k8s:~/oom/kubernetes/oneclick# kubectl describe service dcaegen2 --namespace onap-dcaegen2 Name: dcaegen2 Namespace: onap-dcaegen2 Labels: app=nginx Annotations: <none> Selector: app=nginx Type: LoadBalancer IP: 10.43.5.189 External IPs: 84.39.51.47 Port: aai-service 8443/TCP NodePort: aai-service 30600/TCP Endpoints: 10.42.236.229:8443 Port: dmaap 3904/TCP NodePort: dmaap 30601/TCP Endpoints: 10.42.236.229:3904 Port: sdc-be 8443/TCP NodePort: sdc-be 30602/TCP Endpoints: 10.42.236.229:8443 Port: pdp 8081/TCP NodePort: pdp 30603/TCP Endpoints: 10.42.236.229:8081 Port: msbapigw 80/TCP NodePort: msbapigw 30604/TCP Endpoints: 10.42.236.229:80 Port: multicloud-tinanium 9005/TCP NodePort: multicloud-tinanium 30605/TCP Endpoints: 10.42.236.229:9005 Session Affinity: None 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<UrlBlockedError.aspx>", 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]";, 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 Abdelmuhaimen Seaudi Orange Labs Egypt Email: [email protected]<mailto:[email protected]> Mobile: +2012 84644 733 _________________________________________________________________________________________________________________________ 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
