"Wipe Task" run amok.
-
Fog is up to date version 1.5.7
-
@vangrimoire said in "Wipe Task" run amok.:
This has set a task which wipes out both the target drive as well as the image associated with the host.
I’d need to do some testing on this. I can hardly believe what you described can happen just from scheduling a wipe task". Give me a bit more time to try and replicate this.
Are you sure the image itself was removed? Do you mean the host lost the image association or is the image definition itself gone? What about the actual data on disk? Is
/images/#IMAGENAME#on your disk still existent? -
@vangrimoire I have done some testing with “Normal Wipe” and I can’t replicate anything of what you mentioned. Image still exists in
/images/teston my server disk as well as the image definition and association to that host in the web UI. The only thing that got wiped is the disk of the target host as expected.Are you absolutely sure there is no other user playing with the web UI while you write this?
Don’t get me wrong. What you describe sounds terrible and FOG should never do something like this but from what I understand about it it’s almost impossible to make this happen by scheduling and running a wipe task (which essentially is only meant as wipe the target disk but nothing else!)
-
Oh it was terrible, it looks like the images are still there by browsing, but somehow unlinked in the interface. I deleted the hosts involved and recovered my images - hesitant to hit the “wipe task”.
-
@vangrimoire none this makes sense at all. Wipe tasks are available but the only piece of that updates the database is checking in, and completing the task. At no point is it referencing an image or making updates to the image table.
Did you create the task and start it, then upgrade your fog server? I ask this because there is a potential issue of fog server is Ubuntu and you upgrade your server, it will try to install mariadb which creates a new instance of the database.
-
actually I"ve still got one
it reads 0.00 iB
-
holy crap, it’s just an update to the size registry after a wipe task
-
@vangrimoire that makes sense. That data is just a nice to have. It tries to calculate it during imaging tasks and likely resets it for any task. There is also a service that runs to update the data too. It is not indicative of a problem though.
-
@Tom-Elliott just confusing because it was attached to the image screen after the task had run on the host. I see what’s going on now though.
-
Marking as solved as we have addressed the size-reset to zero issue on client checkin already in
dev-branch: https://github.com/FOGProject/fogproject/commit/9ff877627de44309f9eef8b07587efdb918d3d1e
