Mark, Did you also include checking for volumes and snapshots? This to be sure you don't delete things still needed. Check internal templates as well. These and any "all zones" templates could be in the way, I am hesitant to manipulate the DB but when all else fails this sometimes does solve such issues. It can also break things so your "leery" disposition makes sense.
This can be a daunting task if your cloud is old, but: check snapshot_store_ref, template_store_ref and volume_store_ref for any items that might be still valuable and or should have been deleted. hope this helps, On Thu, Feb 15, 2024 at 4:33 PM Mark Winnemueller <[email protected]> wrote: > > Hello CloudStack users, > > Using CloudStack V 4.18.1.0 I cannot delete my secondary storage store1 > due to "Cannot delete image store with active templates backup!". I > have tried migrating the data to store3, and CloudStack says that it > succeeded, but the data is still on the existing store1 and I'm not > seeing all of the data on store2. > > Background: > > I think this is what confused things. I have gluster NFS across three > machines with ganesha and was using that as secondary storage (picking > one of the IP addresses of the gluster cluster). Because this is fragile > I added keepalived to the gluster machines and added that as secondary > storage. To be clear - they reference the same physical media. That's > when I found out that Cloudstack would not delete store1 (because there > is still data there). > > My first attempt to fix this was to create yet a third Secondary storage > on our TrueNAS box. Migrating data to that storage yields "Successfully > completed migrating Image store data" and "Cannot delete image store > with active templates backup!" when trying to delete the primary storage. > > It seems that there are 2 ways to solve this - 1 is to manually move the > data to store3, and then attempt to remove store1. The second is to > change MySQL image_store table's removed value. The > cloud.image_store.parent value is NULL for the two image stores, so I'm > a little leery of that solution. > > Any help you can provide on the proper way to solve this will be > appreciated. > > Thanks, > > Mark > > -- > Mark Winnemueller > reThought DevOps Engineer > 719.480.4609 > [email protected] > > -- > > > > > > > > > > Operating under CA license #0M61234 > > > > NOTICE: You cannot bind, > alter or cancel coverage without speaking to an authorized representative > of reThought Insurance. Coverage cannot be bound without written > confirmation from an authorized representative of reThought Insurance. This > e-mail and any files transmitted with it are not encrypted and may contain > privileged or other confidential information and is intended solely for the > use of the individual or entity to whom they are addressed. If you are not > the intended recipient or entity, or believe that you may have received > this e-mail in error, please reply to the sender indicating that fact and > delete the copy you received. In addition, you should not print, copy, > retransmit, disseminate, or otherwise use this information. > > -- Daan
