Hi, could it be just a coincidence that the migration failed? I found out just recently (and I updated the launchpad bug you mention accordingly) that if you query keystone for a project specific resource with the '--project' flag, it will first try the provided argument as project ID, then as project name. So for example this results in such a warning: openstack volume list --project admin 2025-03-12 14:45:56.258292 2025-03-12 14:45:56.257 43438 WARNING keystone.server.flask.application [req-d6484ff3-32a1-417f-8355-2d1af2369186 0358b2f4e1a846a28dd516ee8695db82 8e9355b6feef45d9b7d8b379a08264c9 - default default] Could not find project: admin.: keystone.exception.ProjectNotFound: Could not find project: admin. Since you can't tell keystone if you mean ID or Name, it simply tries both. And in your case someone might have run a command with '--project 6008439893ca4d80ab933cf3b0b5fef0', or can you rule that out? Or maybe it could be some old instance which has different (image) metadata than other VMs? Did this happen only once or multiple times? Regards, Eugen Zitat von İzzettin Erdem <root.mch@gmail.com>:
Hi, I faced to an odd issue; while migrating some servers, keystone threw an exception and migration aborted
- Could not find project: 6008439893ca4d80ab933cf3b0b5fef0
When I checked, a project with this ID does not exist, but the key point is it's not a project ID, it's an ID of a user.
I googled this problem but couldn't find more information except this [1] <https://bugs.launchpad.net/keystone/+bug/2062247>.
PS: _ mysql logs were fine, didn't see weird queries _ keystone works fine _ openstack version kolla-ansible/train
Do you have any ideas?
Thanks, İzzettin