Andrew Wong

Thank you @amnonh! What is the protocol for getting this merged?

The kgoverifier sequential consumer logs stop at 17:15, but node 2 continues to receive requests from the consumer and logs messages like: ``` TRACE 2022-11-10 17:15:19,514 [shard 0] kafka -...

This looks like #7231, I see in the seq consumer logs we're also hanging at `PollFetches()`: ``` time="2022-11-10T17:15:14Z" level=debug msg="Sequential read topic-rqojdzmgrf/0 o=99999..." time="2022-11-10T17:15:14Z" level=debug msg="Consumed 000000.000000000000099999 on p=0 at...

I'm not sure I follow what was merged here and what wasn't, but I think I hit the issue reported on v22.2.x: https://buildkite.com/redpanda/redpanda/builds/22776#01863183-571a-42e3-9461-403e43a11e74

Just to clarify the signals here, @kargh do you know roughly when you started upgrading the first node? Looks like Nov 16 15:35:47 is when things started going bad with...

> The backported test is failing (i.e. presumably this is when it tries to upgrade from 22.1.x to 22.2.x) > > Given that most of these upgrades in the field...

Some upgrade tests start out pegging to a specific version as a means to test the onboarding behavior when going from a version that doesn't support feature Foo to a...

We discussed this a bit and we concluded that moving forward we should categorize our existing upgrade tests: - Tests that only test the onboarding of a feature. Such tests...

From Redpanda's perspective, a couple observations: - this node believes it isn't a cluster founder, meaning it either found that another node has a cluster UUID (only possible if we...

Another thing I'm confused about is why this is only happening only sometimes, if the issue truly is that DNS setup cannot proceed until the node exposes its admin endpoint.