sal-pda service is not working

Bug #2065785 reported by Ankica Barisic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NebulOuS
Triaged
Medium
Ankica Barisic

Bug Description

Hi,

I tested today and it seems that nebulous-sal-pda service is not healthy with the last deployments (see screenshot)

Can you please check what is causing this?

In a case that is not something specific to nebulous environment (it was working before with no problems) i will ask you to deploy sal as we defined without splitting the services in separate scripts and notify me to perform the test.

Revision history for this message
Ankica Barisic (akki55) wrote :
Revision history for this message
Radosław Piliszek (yoctozepto) wrote :

It is not a platform problem, SAL's PDA resets connections inside the container itself:

$ kubectl debug -n nebulous-cd nebulous-sal-6cbc857dcd-hvm24 -it --image=nicolaka/netshoot

...

 nebulous-sal-6cbc857dcd-hvm24  ~  ss -tnlp
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 80 0.0.0.0:3306 0.0.0.0:*
LISTEN 0 1 0.0.0.0:9001 0.0.0.0:*
LISTEN 0 100 *:8080 *:*
LISTEN 0 80 [::]:3306 [::]:*
LISTEN 0 1 [::ffff:127.0.0.1]:8005 *:*

 nebulous-sal-6cbc857dcd-hvm24  ~  curl 127.0.0.1:9001
curl: (56) Recv failure: Connection reset by peer

 nebulous-sal-6cbc857dcd-hvm24  ~  ip -4 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
5: eth0@if233: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default link-netnsid 0
    inet 10.244.4.224/24 brd 10.244.4.255 scope global eth0
       valid_lft forever preferred_lft forever

 nebulous-sal-6cbc857dcd-hvm24  ~  curl 10.244.4.224:9001
curl: (56) Recv failure: Connection reset by peer

Changed in nebulous:
assignee: Radosław Piliszek (yoctozepto) → Ankica Barisic (akki55)
status: New → Triaged
Ankica Barisic (akki55)
Changed in nebulous:
importance: High → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.