Till!

``` Oct 14 15:28:26 node-001.luzilla update_engine[7130]: I20251014 15:28:26.474259 7130 libcurl_http_fetcher.cc:320] Transfer completed (200), 305 bytes downloaded Oct 14 15:28:26 node-001.luzilla update_engine[7130]: I20251014 15:28:26.474316 7130 omaha_request_action.cc:617] Omaha request response: Oct 14...

@ervcz I've tried `update_engine_client -update` multiple times before I went with `flatcar-update`. We recently switched to a local Nebraska to better coordinate updates. Is the protocol incompatible? I see these...

We are in the process of transitioning away from cgroupv1, so I found this in the log - would be nice if this is elevated: ``` Flatcar version 4187 or...

This is another server where I am updating right now. The fix was to reboot it (since I disabled cgroupv1 already) and now the update continues. I think it's a...

The transition itself is not a biggie. We've also been tracking it internally for a long time. My issue is that none of the problems are elevated. The update client...

Maybe all of this is feedback for the update engine rebuild? :) --- > I would have some follow-ups to better understand your situation. > > > I've tried update_engine_client...

Can you comment how you setup your local resolver? The helm chart contains an unbound sidecar as an example which seems to work. How's your setup different?

Do you happen to have examples for the responses so we can write a test later. I am a bit stretched on time, so I appreciate your input.

@lapo-luchini I am torn on this. So to summarize: you expect the exporter to yield a different response when people use an open resolver? Or do you want to ignore...

It sounds super complicated to maintain all these specifics?