I took a look at the bug report and downloaded the ndb error report.
I also looked in the code to see where the error could come from.
The only reason for the bug that I can see so far is that
for some reason the MySQL Server decides to do both an Add partition
and alter the READ BACKUP flag at the same time. This will generate
the error you get.
Obviously from SQL you haven't asked for an add partition, so this would
be a bug in the storage engine if it did.
The reason I am suspecting this is also that I noted that in the configuration
you have set NoOfFragmentLogParts=8. This is normally only done when you want
to have 8 LDM threads. In your config you have only 4 LDM threads (derived from
MaxNoOfExecutionThreads=8.
If you have changed the config recently in this aspect I would expect that you
hit this bug for older tables and not for newer tables.
You can try and see what happens if you execute the following command on the
faulty tables.
ALTER TABLE <tablename>, algorithm=inplace REORGANIZE PARTITIONS;
and after that the failing command again.