One more reply to myself.
For reasons that are not quite clear we found that there were log
directories left on brokers that corresponded to topics or partitions that
no longer exist or that no longer reside on a given broker.
Those directories don't and won't have a topicID which is causing kafka
Seems that actually running ./bin/kafka-reassign-partitions.sh to first
generate and then execute to move the topic is working.
I later realized that in a cluster where the metadata have been migrated to
k-raft, the following command: ./bin/kafka-topics.sh --describe
--bootstrap-server broker:9092
