Sounds a legit bug in Nova. We only verify the existing transport url and database connections as being unique for a cell here : https://github.com/openstack/nova/blob/c4cd6ee4615a35a57dd6a2f3cb5a9cbc8653f7ee/nova/cmd/manage.py#L662-L675
That being said, we don't verify that the name is not unique here https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L1116 as there is no UniqueConstraint in the DB on the name field https://github.com/openstack/nova/blob/c4cd6ee4615a35a57dd6a2f3cb5a9cbc8653f7ee/nova/db/api/models.py#L141
Putting it as Triaged then, as I think two cells having the same name (using different transport URLs) could be an issue for the operator.
Sounds a legit bug in Nova. /github. com/openstack/ nova/blob/ c4cd6ee4615a35a 57dd6a2f3cb5a9c bc8653f7ee/ nova/cmd/ manage. py#L662- L675
We only verify the existing transport url and database connections as being unique for a cell here : https:/
That being said, we don't verify that the name is not unique here https:/ /github. com/openstack/ nova/blob/ master/ nova/cmd/ manage. py#L1116 as there is no UniqueConstraint in the DB on the name field https:/ /github. com/openstack/ nova/blob/ c4cd6ee4615a35a 57dd6a2f3cb5a9c bc8653f7ee/ nova/db/ api/models. py#L141
Putting it as Triaged then, as I think two cells having the same name (using different transport URLs) could be an issue for the operator.