I think you changed 'my_ip' to '10.10.0.30' after having it copy-pasted from the install guide as 'MANAGEMENT_INTERFACE_IP_ADDRESS' and tried to use it whit that value.

So that wrong "hostname" got saved in the DB when it should have been a numerical IP@...

You can fix it by doing the following on the controller node:

# mysql -u root -p MY_PASSWORD
use nova;
select * from compute_nodes where host_ip = 'MANAGEMENT_INTERFACE_IP_ADDRESS';

As explained in the installation documentation, host_ip must always be specified in dotted numerical notation, string host names are not allowed...

DAMHIKT

Check that is indeed the problem with the preceding "SELECT" SQL command, then delete the offending rows from your DB, with this one:

# mysql -u root -p MY_PASSWORD
use nova;
delete from compute_nodes where host_ip = 'MANAGEMENT_INTERFACE_IP_ADDRESS';

and restart nova service on the compute node so that it re-register itself properly in the DB...

systemctl start openstack-nova-compute.service

That should do it, be extra careful if your cloud is in production mode, though...

The same solution works in case you tried to use a properly resolving hostname as 'my_ip', thinking that it should work... Just adapt the SQL command to search / delete rows containing your hostname instead of 'MANAGEMENT_INTERFACE_IP_ADDRESS'...

If someone use that recipe to fix his problem, please mark this answer as the solution to this question, thanks...