Public bug reported: Hi,
When we delete a nova-compute service, the 'mapped' field in nova_cell1.compute_nodes table stays at 1 instead of 0 while nova_api.host_mappings related entry is completely removed. By letting that 'mapped' field to 1, it prevents nova-manage cell_v2 discover_hosts command to create the missing mapping. And that way, we can't anymore spawn on that compute because it's not linked to any cell. It may be linked to that bug: https://bugs.launchpad.net/nova/+bug/2077070 To fix, we can use the --by-service option: nova-manage cell_v2 discover_hosts --verbose --by-service like mentioned here: https://bugs.launchpad.net/nova/+bug/2077070/comments/7 A more global fix would be to set the 'mapped' field to 0 at nova- compute service deletion. Environment =========== - fresh Antelope deployment on Debian12 - self provisioned compute id ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/2085135 Title: nova fails to map host which has a provisioned node identity after its nova-compute service was deleted Status in OpenStack Compute (nova): New Bug description: Hi, When we delete a nova-compute service, the 'mapped' field in nova_cell1.compute_nodes table stays at 1 instead of 0 while nova_api.host_mappings related entry is completely removed. By letting that 'mapped' field to 1, it prevents nova-manage cell_v2 discover_hosts command to create the missing mapping. And that way, we can't anymore spawn on that compute because it's not linked to any cell. It may be linked to that bug: https://bugs.launchpad.net/nova/+bug/2077070 To fix, we can use the --by-service option: nova-manage cell_v2 discover_hosts --verbose --by-service like mentioned here: https://bugs.launchpad.net/nova/+bug/2077070/comments/7 A more global fix would be to set the 'mapped' field to 0 at nova- compute service deletion. Environment =========== - fresh Antelope deployment on Debian12 - self provisioned compute id To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2085135/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp