coproc: failure in WasmCreateTopicsTest.verify_materialized_topics_test

[ajfabbri]

Similar to 3745, but in the CreateTopics test...

test_id:    rptest.tests.wasm_topics_test.WasmCreateTopicsTest.verify_materialized_topics_test
--
  | status:     FAIL
  | run time:   48.585 seconds
  |  
  |  
  | Exception('Bad config, expected: [<rptest.clients.rpk.RpkPartition object at 0x7f2611185580>, <rptest.clients.rpk.RpkPartition object at 0x7f26111c7c10>, <rptest.clients.rpk.RpkPartition object at 0x7f26111c7220>] observed: [<rptest.clients.rpk.RpkPartition object at 0x7f261104da60>, <rptest.clients.rpk.RpkPartition object at 0x7f2610f7b040>, <rptest.clients.rpk.RpkPartition object at 0x7f2610f7b190>]')
  | Traceback (most recent call last):
  | File "/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 135, in run
  | data = self.run_test()
  | File "/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 215, in run_test
  | return self.test_context.function(self.test)
  | File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
  | r = f(self, *args, **kwargs)
  | File "/root/tests/rptest/tests/wasm_topics_test.py", line 51, in verify_materialized_topics_test
  | raise Exception("Bad config, expected: %s observed: %s" %
  | Exception: Bad config, expected: [<rptest.clients.rpk.RpkPartition object at 0x7f2611185580>, <rptest.clients.rpk.RpkPartition object at 0x7f26111c7c10>, <rptest.clients.rpk.RpkPartition object at 0x7f26111c7220>] observed: [<rptest.clients.rpk.RpkPartition object at 0x7f261104da60>, <rptest.clients.rpk.RpkPartition object at 0x7f2610f7b040>, <rptest.clients.rpk.RpkPartition object at 0x7f2610f7b190>]

[ajfabbri]

I plan on disabling this shortly--to solidify CI while we work on improvements (see linked issue)

[andrewhsu]

seen on 2022-02-19: https://buildkite.com/redpanda/redpanda/builds/7485#541cd77c-33d9-42c9-9301-f7d5bdd049d6/1498-7144

[ajfabbri]

recent failure (from before I just disabled this test): https://buildkite.com/redpanda/redpanda/builds/7506#9608c195-ee9c-4dc3-9ce6-72cfb501db42

[graphcareful]

Going to elaborate why the test failed:

[DEBUG - 2022-02-21 07:50:58,976 - rpk - _execute - lineno:388]: PARTITION  LEADER  REPLICAS  LOG-START-OFFSET  HIGH-WATERMARK
0          2       [1 2 3]   0                 0
1          3       [1 2 3]   0                 10
2          3       [1 2 3]   0                 0

[DEBUG - 2022-02-21 07:50:59,127 - rpk - _execute - lineno:375]: Executing command: ['/var/lib/buildkite-agent/builds/buildkite-amd64-builders-i-0aa53ba031d0daf20-1/redpanda/redpanda/vbuild/debug/clang/dist/local/redpanda/bin/rpk', 'topic', '--brokers', 'docker_n_7:9092,docker_n_17:9092,docker_n_21:9092', 'describe', 'topic-roircxjryu._output_1_', '-p']
[DEBUG - 2022-02-21 07:50:59,196 - rpk - _execute - lineno:388]: PARTITION  LEADER  REPLICAS  LOG-START-OFFSET          HIGH-WATERMARK
0          2       [1 2 3]   0                         0
1          3       [1 2 3]   NOT_LEADER_FOR_PARTITION  10
2          3       [1 2 3]   0                         0

The test is doing a deep comparison and the NOT_LEADER_FOR_PARTITION is causing this to fail.

[dotnwat]

closing this ci-failure ticket. the test is disabled, and there is no scheduled coproc work/maintenance. in the meantime it is polluting the ci-failure clean-up effort statistics.