weizhouapache commented on PR #7239: URL: https://github.com/apache/cloudstack/pull/7239#issuecomment-1847107331
> @weizhouapache can you please share the state of VMs `admin-001-001` and `i-2-162-VM` in your database after doing your test? And about fixing an issue with Veeam by changing the unmanage/manage process, I think having two VMs with same `instance_name` in database is a inconsistency that is being generated by the manage/import VMware VMs. The internal name is expected to be unique. @SadiJr here you are ``` mysql> select id,name,uuid,instance_name,display_name,state,created,removed from vm_instance where id in (162,225); +-----+---------------+--------------------------------------+---------------+---------------+-----------+---------------------+---------------------+ | id | name | uuid | instance_name | display_name | state | created | removed | +-----+---------------+--------------------------------------+---------------+---------------+-----------+---------------------+---------------------+ | 162 | admin-001-001 | c13f4662-dd08-4f24-abd3-c1b581a3ecd2 | i-2-162-VM | admin-001-001 | Expunging | 2023-12-01 08:22:55 | 2023-12-07 20:00:16 | | 225 | i-2-162-VM | a974a38d-5b9a-40d2-a0fb-feb80ef88762 | i-2-162-VM | NULL | Stopped | 2023-12-07 20:01:01 | NULL | +-----+---------------+--------------------------------------+---------------+---------------+-----------+---------------------+---------------------+ 2 rows in set (0.00 sec) ``` the original one is in `Expunging` state and `removed` field is not empty. so it does not impact the new vm. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
