Hi Hideshi,
Apologies for the delay in the response. The bz had been triaged as valid and was in our backlog. I've started work on it upstream. I'm afraid there is no workaround besides manual database editing.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (openstack-nova bug fix advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4393