little more update :
further testing on other onap casablanca setup pointed next problem from the
same category
this time NodePort collision took place with xdcae-ves-collector and
vvp-ext-haproxy
30235 is default nodeport for ves based on its blueprint :
[root@dev-dcaegen2-dcae-bootstrap-6c58dbc695-k8xfj blueprints]# grep -A3
external_port: k8s-ves.yaml
external_port:
type: string
description: Kubernetes node port on which collector is exposed
default: "30235"
[root@dev-dcaegen2-dcae-bootstrap-6c58dbc695-k8xfj blueprints]#
and other service like vvp-ext-haproxy should not occupy it
root@esohn30-lab20n-tag-957396-rancher-master:~# kubectl -n onap get svc | grep
30235
vvp-ext-haproxy NodePort 10.43.194.44 <none>
80:30590/TCP,443:30235/TCP,22:30477/TCP,9000:31731/TCP
4h
root@esohn30-lab20n-tag-957396-rancher-master:~#
W dniu 28.02.2019 o 16:22,
[email protected]<mailto:[email protected]> pisze:
hey
met port collision issue also with msb-iag and vvp-jenkins services
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# helm deploy
dev-msb local/onap --namespace onap --verbose
fetching local/onap
Release "dev-msb" does not exist. Installing it now.
Error: release dev-msb failed: Service "msb-iag" is invalid:
spec.ports[0].nodePort: Invalid value: 30280: provided port is already allocated
dev-msb 1 Thu Feb 28 14:46:57 2019 FAILED
msb-3.0.0 onap
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# kubectl -n onap
get svc | grep 30280
vvp-jenkins NodePort 10.43.34.61 <none>
8080:30280/TCP
3h
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# kubectl -n onap
describe svc vvp-jenkins
Name: vvp-jenkins
Namespace: onap
Labels: app=vvp-jenkins
Annotations: <none>
Selector: app=vvp-jenkins
Type: NodePort
IP: 10.43.34.61
Port: jenkins 8080/TCP
TargetPort: 8080/TCP
NodePort: jenkins 30280/TCP
Endpoints: 10.42.154.77:8080
Session Affinity: None
External Traffic Policy: Cluster
Events: <none>
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
salutes
marek
W dniu 28.02.2019 o 13:04,
[email protected]<mailto:[email protected]> pisze:
hey All
in Casablanca just met following error during sdc deployment :
fetching local/onap
release "dev" deployed
release "dev-aaf" deployed
release "dev-aai" deployed
release "dev-appc" deployed
release "dev-clamp" deployed
release "dev-cli" deployed
release "dev-consul" deployed
release "dev-contrib" deployed
release "dev-dcaegen2" deployed
release "dev-dmaap" deployed
release "dev-esr" deployed
release "dev-log" deployed
release "dev-msb" deployed
release "dev-multicloud" deployed
release "dev-nbi" deployed
release "dev-oof" deployed
release "dev-pnda" deployed
release "dev-policy" deployed
release "dev-pomba" deployed
release "dev-portal" deployed
release "dev-robot" deployed
release "dev-sdc" deployed
release "dev-sdnc" deployed
release "dev-sniro-emulator" deployed
release "dev-so" deployed
release "dev-uui" deployed
release "dev-vfc" deployed
release "dev-vid" deployed
release "dev-vnfsdk" deployed
release "dev-vvp" deployed
dev-sdc 1 Thu Feb 28 11:27:20 2019 FAILED
sdc-3.0.0 onap
sdc re-deploy gave
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# helm deploy
dev-sdc local/onap --namespace onap --verbose
fetching local/onap
Release "dev-sdc" does not exist. Installing it now.
Error: release dev-sdc failed: Service "sdc-wfd-fe" is invalid:
spec.ports[0].nodePort: Invalid value: 30256: provided port is already allocated
dev-sdc 1 Thu Feb 28 11:34:16 2019 FAILED
sdc-3.0.0 onap
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
looks dcae-pnda-mirror service is using reguired port 30256
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# kubectl -n onap
get svc | grep 30256
dcae-pnda-mirror LoadBalancer 10.43.212.32 192.168.0.22
80:30256/TCP
9m
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes# kubectl -n onap
describe svc dcae-pnda-mirror
Name: dcae-pnda-mirror
Namespace: onap
Labels: app=dcae-pnda-mirror
chart=dcae-pnda-mirror-3.0.0
heritage=Tiller
release=dev-pnda
Annotations: <none>
Selector: app=dcae-pnda-mirror,release=dev-pnda
Type: LoadBalancer
IP: 10.43.212.32
LoadBalancer Ingress: 192.168.0.22
Port: client 80/TCP
TargetPort: 80/TCP
NodePort: client 30256/TCP
Endpoints: <none>
Session Affinity: None
External Traffic Policy: Cluster
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal EnsuringLoadBalancer 22m service-controller Ensuring load balancer
Normal EnsuredLoadBalancer 21m service-controller Ensured load balancer
root@esohn30-lab19n-tag-957238-rancher-master:~/oom/kubernetes#
has someone maybe faced the same so far ?
salutes
marek
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15803): https://lists.onap.org/g/onap-discuss/message/15803
Mute This Topic: https://lists.onap.org/mt/30162607/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
