FOG 1.5.0 RC2 Cannot Delete Image From Storage Node/Group
-
Sebastian, I know we delete records when we were looking at the install here over the weekend. Would any of the deletes we did apply to what Tom’s talking about?
Jim
-
@Jim-Graczyk As far as I remember we only did SQL queries but did not try to delete… should have. Please contact me in chat so we can try…
-
Definitely not a mysql ACL/permission issue as we were able to delete entries from that table by hand. Tom got a dump now and seems to have found what is causing this. He’s working on a fix.
-
Fix is now in the
workingbranch. I accidentally pushed into thedev-branchas well, so you could just do a pull from dev-branch and reinstall and revel in the success. (Hopefully). -
@Tom-Elliott Update Worked! Location plugin was installed when the update was made. Was able to disassociate several images from several storage groups.
We can consider this resolved.
Thanks.
Jim -
@tom-elliott I’ve got the same exact problem happening as @Jim-Graczyk and I’ll try to be more descriptive.
I have an image stored on a storage group “3r” but when I select the image and view its Storage Group two groups are listed “2r” and “3r” with a radio button check mark beside 3r, which I take to mean primary although there is no header text for that column so it’s not clear what that check is for. The available options include check boxes beside Storage Group name and beside each listed node, in this case 2r and 3r, and an Update primary group “Update” button and a Remove selected groups “Remove” button.
I’ve confirmed that the image does exist in both images folders on both nodes 2r and 3r but I only want it to occupy 3r, the image’s primary storage group. When I directly remove the image by deleting it from the 2r images folder it gets copied back, thereby suggesting an accurately reflected status on the Image Management/Storage Group page. When I select the checkbox beside 2r and click the Remove button an Image Update Success “Image Updated” popup appears but 2r never disappears from the list even after refreshing or navigating away and back again and the image still gets copied back to 2r if deleted directly.
Each node is set as a Master Node with its own Storage Group; node2r:group2r and node3r:group3r
I actually have this occurring with several images but not all, most images are fine being listed in only one storage group and existing in the one images folder. It appears something is gummed up with the database records that the GUI cannot correct.
Additionally, but a separate problem is, I have images in the database listed in 2r that are really in 3r and vise versa and I wish I could just change the reference via the GUI.
-
@mjaskowski Would you care to share a copy of your database with me so I can figure out what the issue is? Don’t post it here, PM me.
