Moved back to Bugs. I wasn’t saying this wasn’t a bug, I just wanted to know what the bug was more cleanly.

The bug was the text being written to the database only showed updated for any deleted item. This was due to an ajax check. When we delete something, we are doing so via ajax. The checks were only allowing writing to the db if the item in use was not coming from ajax.

While this is still valid, the change to more appropriately write data based on the action should have been available through user based ajax calls. (You had to interact to login in order to delete an item).

I set one of my hosts to pending and I see what yo’re seeing.

I don’t know german very well so I didn’t know what was being said there. Now I see it says:

“Requires templates to process”

I fixed it. Will be fixed for RC-21.

@Tom-Elliott Yes solved. We need to make an SQL statement though that will set all images that only have one storage group to make that group primary. Because we have a ton of images that have no primary group but also only have one group.

@Tom-Elliott You’re the man, Tom!

Fixed will be released for RC-21.

@Tom-Elliott

Don’t be sorry! Thanks for all you do!

The storms have passed and all sites are back online. I’m not sure how I can verify that the image replicator doesn’t quit if a node is offline. I guess I could setup a test at home but it might not be the same. Because in the real-world OP, the primary group that had the image was MIA. I’m happy you made efforts to solve it but at this moment I cannot confirm or deny they work.

It seems ok this morning

fix after update

thanks a lot !!

@Matthieu-Jacquart yes did so just some seconds ago 😉 working again 😉

alt text

Regards X23

Ok thank you, everything works perfectly, i dont know why it was not working anymore…

The F12 thing didn’t work for me. Ctrl + F5 seems to work.

I probably should have said this earlier but,

at my building, we have a stand-alone fog server. The bandwidth chart for it works perfectly as expected.

At our administration center, we have a large fog setup. The main server has two storage nodes defined for it, and there are 14 other storage nodes that are elsewhere but managed by this main server. Only one of the main server’s storage nodes is “graph enabled”. All other remote storage nodes have their graphs disabled. This is the system with the graph issue.

RC-19 should address this issue for you more appropriately.

@Tom-Elliott Nice - thanks!

@cojohnson said in FOG Registration Error. Hostname with that name already exists:

It renamed and started working properly after i reset encryption data. However, I have had to do that every time

This time isn’t the same if you followed what I asked, because you said you previously had to press the reset button twice, I asked you to press it once.

@Tom-Elliott Using the command you posted fixed the problem. Thanks for the quick fix.

Tom says he has fixed this in RC-17, which is now released because this was a pretty major bug - in terms of hindering everyday I.T. operations.

@Tom-Elliott
Yes I confirm
Thank you

@Tom-Elliott Thanks Tom. I’ll update and confirm.

@Tom-Elliott This fix works for me. Thanks!