tsinik-dw commented on issue #5915:
URL: https://github.com/apache/cloudstack/issues/5915#issuecomment-1061478770


   Hi @nvazquez, 
   
   here is the output of the SQL queries:
   
   select * from volumes where id = 132;
   ~~~
   
"id","account_id","domain_id","pool_id","last_pool_id","instance_id","device_id","name","uuid","size","folder","path","pod_id","data_center_id","iscsi_name","host_ip","volume_type","pool_type","disk_offering_id","template_id","first_snapshot_backup_uuid","recreatable","created","attached","updated","removed","state","chain_info","update_count","disk_type","vm_snapshot_chain_size","iso_id","display_volume","format","min_iops","max_iops","hv_ss_reserve","provisioning_type"
   
132,2,1,1,,,,DATAVOL-1,"09243386-b5f2-4920-afc3-3505d2ee311c",2147483648,,"0f7024ca-e21f-4398-a236-16536f978755",,1,,,DATADISK,IscsiLUN,21,,,0,2022-03-03
 07:52:32,,2022-03-03 12:32:20,2022-03-03 
12:32:20,Expunged,,14,,,,1,VHD,,,0,thin
   ~~~
   Please note, that this volume is now in `Expunged` state because I tried to 
delete it after the unsuccessful migration and it didn't worked.
   
   Also, the following disk offering output is currently the following but 
there have been manual changes to the values is several fields.
   select * from disk_offering where uuid = 
"5b764ddb-ea60-40b1-8ff5-586953266e92";
   ~~~
   
"id","name","uuid","display_text","disk_size","type","tags","recreatable","use_local_storage","unique_name","system_use","customized","removed","created","sort_key","display_offering","customized_iops","min_iops","max_iops","bytes_read_rate","bytes_read_rate_max","bytes_read_rate_max_length","bytes_write_rate","bytes_write_rate_max","bytes_write_rate_max_length","iops_read_rate","iops_read_rate_max","iops_read_rate_max_length","iops_write_rate","iops_write_rate_max","iops_write_rate_max_length","state","hv_ss_reserve","cache_mode","provisioning_type"
   22,SF DO 2 (2 GB) 2222-4444,"5b764ddb-ea60-40b1-8ff5-586953266e92",SF DO 2 
(2 GB) 2222-4444,2147483648,Disk,sf,0,0,,0,0,,2022-03-03 
08:01:30,0,1,0,2222,4444,,,,,,,,,,,,,Active,100,none,thin
   ~~~
   
   However, I did tried similar volume migrations with the following volume and 
disk offering records. As you can see the volume size is 2GB, and the Disk 
Offering is if 12GB (I tried with 7GB too).
   
   VOLUME
   ~~~
   
"id","account_id","domain_id","pool_id","last_pool_id","instance_id","device_id","name","uuid","size","folder","path","pod_id","data_center_id","iscsi_name","host_ip","volume_type","pool_type","disk_offering_id","template_id","first_snapshot_backup_uuid","recreatable","created","attached","updated","removed","state","chain_info","update_count","disk_type","vm_snapshot_chain_size","iso_id","display_volume","format","min_iops","max_iops","hv_ss_reserve","provisioning_type"
   
134,2,1,1,,131,1,DATAVOL-2,feab49ab-7381-4d55-a86a-6d2c51faa8dc,2147483648,,"03394dc4-d95a-47cc-8fb3-9950e92a2b44",,1,,,DATADISK,IscsiLUN,21,,,0,2022-03-03
 12:32:59,2022-03-03 12:34:34,2022-03-03 12:41:32,,Ready,,8,,,,1,VHD,,,0,thin
   ~~~
   
   DISK OFFERING
   ~~~
   
"id","name","uuid","display_text","disk_size","type","tags","recreatable","use_local_storage","unique_name","system_use","customized","removed","created","sort_key","display_offering","customized_iops","min_iops","max_iops","bytes_read_rate","bytes_read_rate_max","bytes_read_rate_max_length","bytes_write_rate","bytes_write_rate_max","bytes_write_rate_max_length","iops_read_rate","iops_read_rate_max","iops_read_rate_max_length","iops_write_rate","iops_write_rate_max","iops_write_rate_max_length","state","hv_ss_reserve","cache_mode","provisioning_type"
   25,SF DO 12 GB,deea8a00-3024-4ccd-ae95-0df023c4e76d,SF DO 12 
GB,12884901888,Disk,sf,0,0,,0,0,,2022-03-03 
12:31:32,0,1,0,1111,2222,,,,,,,,,,,,,Active,200,none,thin
   ~~~


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to