Hi Mevludin, Is there a migration in-progress for the secondary store in question. If so, it could lead to templates (template_store_ref), volumes (volume_store_ref) and snapshots (snapshot_store_ref) being in the Migrating state.Templates (or any other data object) in the Allocated state shouldn't be an issue. But for those in Migrating state, one could either wait for the operation to complete / timeout, or set the respective records (those that are in Migrating state) to Ready state. However, please verify these steps on a test environment before proceeding to perform them on a production system.
Thanks, Pearl On Wed, May 24, 2023 at 11:22 AM Mevludin Blazevic <[email protected]> wrote: > Hi all, > > while trying to migrate from one secondary storage to another, I get the > following error: "Complete migration failed as there are data objects > which are not Ready - i.e, they may be in Migrating, creating, copying, > etc. states" > > On the UI, there are no Templates or ISOs which are not ready or in > error state, I can only see in "template_store_ref" that there are some > rows which consists of the states "allocated, migrating" etc. but most > of them are linked to the same template_id which is ready. > > How to solve the issue? Is is safe to delete all table rows with the > corresponding template states? Which tables I need to edit? > > Best, > Mevludin > -- Pearl Dsilva
