Multinode - doesnt work after the stop and start commands were executed

Reported by customer:

We set up a multi-node system with the ansible instructions that were on the git using our own servers. We verified the system was running for Columnstore with multiple nodes, using storage manager and the S3 for storage. We tried the stop and start of the cluster commands as shown in the git (using curl commands). When these came back up, the system was in a read only state and not stable. Any columnstore table that tried to be queried would point to it not existing in the Columnstore engine, which indicates an issue with the dbrm or frm files. I checked that the frm exists for this. It is possible that further documentation that will be released may address some of these issues.

They reported it looks similar to MCOL-4226, but 4226 couldnt get the system going and in this issue they achieved a good install and startup, but it failed to work after stop/start command