Closed gabrielmougard closed 1 year ago
@monstermunchkin @tomponline have you witnessed this already ?
Please show "lxc config show"
$ lxc config show
config: {}
This is not a bug.
I can reproduce what you're seeing when using the browser. That must have to do with caching. If you try the same thing with curl, you cannot connect to the server. Also, the output of ss -tln
doesn't show that it's listening on the port anymore.
Thanks!
Required information
With no signal handling whatsoever (i.e, when the listener closes, is this goroutine terminated ? Because it seems I still can access the endpoint eventhough this one is not listening for new incoming data anymore)
I didn't check if this happens for other existing endpoints but I noticed the same behaviour here with this new endpoint I recently introduced.
Is it a bug or a feature (a.k.a is it intended to keep the endpoint reachable eventhough the property defining the endpoint address is not in the server core config) ?
Steps to reproduce
lxc config set core.metric_address :8444
http://0.0.0.0:8444/1.0
in a browser and see the metrics.lxc config unset core.metric_address
lxc config show
, nowcore.metric_address
should have disappeared which is as expected.closing socket
in the log, proof thatfunc (e *Endpoints) closeListener(kind kind) error
has been called successfully.http://0.0.0.0:8444/1.0
in a browser and witness that the metric server is still reachable (we don't want that).