Broker deregistration after connector shutdown seems not to work properly

[ip312]

Bug Report

Description

After shutdown of the connector I can further see it on the MDS test broker.
https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F457711283

Expected Behavior

After shutdown the connector is not visible on the broker anymore.

Observed Behavior

It is visible.

Steps to Reproduce

Steps to reproduce the behavior:

1. Start the local connector in the docker desktop
2. Check, whether the connector is registered on the broker (yes)
3. Shutdown the connector in the docker desktop
4. Check, whether the connector is deregistered (no)

Context Information

• Environment: Local
• Used version: 3.0.1

[tmberthold]

Update
Test-Broker seems to currently not respond at all to IDS Messages-> getting 504 Gateway Timeout as response on messages to the IDS-endpoint https://broker.test.mobility-dataspace.eu/infrastructure

We'll keep looking at this...

[SebastianOpriel]

@ip312 can you clarify on your latest observations regarding the Broker? Does this correlate with this issue?

[ip312]

My assumption is that there are two different things.
At the time i noticed the issue above I was able to register connectors, e.g.
https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F457711283
https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F-1765550025
https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F-1865489203
which were not deregistered after shutdown of these connectors in the docker desktop.

Currently I am not able to register connectors due to the mentioned response problem at the Broker. Also we should wait until the broker is up and running again.

[ip312]

Now I can confirm the issue. I have just started the docker desktop and registered this connector
https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F457711283
After that I have stopped the docker container via docker desktop, but as you can see, the connector is still registered.

[SebastianOpriel]

@ip312 wrote:

The deregistration problem seems to be still there. Started the 3.1.0. version now, the connector reported to the broker, now I stopped that, but it is still there. https://catalog.test.mobility-dataspace.eu/connector/connector?id=https%3A%2F%2Fbroker.test.mobility-dataspace.eu%2Fcatalog%2F457711283 .
Branch 3.1.0 is missing, so I took main

• Create branch 3.1.0

[SebastianOpriel]

I could reproduce the issue.
docker compose up with CTL + C gracefully stopps the containers, but edc-extensions exits with code 137

Tried instead:

docker compose up -d
docker compose stop -t 100

But still runs into timeout of 100 sec.

[ip312]

I think, this one can be closed. It's not relevant anymore.