Red Hat Bugzilla – Bug 990524
storage_pool_id column at async_tasks always contains the empty GUID value
Last modified: 2015-03-04 19:19:02 EST
Description of problem:
The value of storage_pool_id at async_tasks table always equals to the empty guid value (00000000-0000-0000-0000-000000000000) instead of holding the id of the the data center (storage pool) which the tasks runs on its SPM.
This did not happen in version 3.2, as from 3.3, the tasks are created in DB prior to their execution on VDSM.
The "InsertOrUpdateAsyncTasks" stored procedure never updated the storage pool id, and once vdsm task id is returned to engine, this is the stored procedure being used.
This should be fixed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
At version 3.2 - the task was added to db when vdsm task id was returned from the SPM host, and the Insertasync_tasks stored procedure which inserts the storage_pool_id is used.
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)