GIT 8056: FOG Server loops after deleting host

[Tom Elliott]

@tmerrick can you try on chrome?

[tmerrick]

Fails also on Chrome. Also, there is now a new pop up re-authorization screen just before it loops.

[Tom Elliott]

@tmerrick re authorization should be happening if the credentials you’re entering are invalid.

[tmerrick]

Nope, it happens every time that I hit delete. This seems to be the cause of the looping.

[Quazz]

@tmerrick What OS is FOG running on?

[tmerrick]

Red Hat 6.

[Quazz]

@Testers Can anyone reproduce this? I’ve had no luck on my end, it works as expected.

[tmerrick]

I do not know if this helps, but the host was part of 3 groups when they were deleted.

[Wayne Workman]

@tmerrick Can you describe, verbatim click-for-click exactly what you’re doing to reproduce this error?

[tmerrick]

Lookup a host.
Then press the Delete menu item
Confirm the removal.
It now pops up a mini screen asking for login/password.
It then says that it is attempting to perform actions - and hangs here.

[Wayne Workman]

@tmerrick I can confirm the issue on my setup. I’m on 8064 and using Firefox 46.0.1

Although, after several attempts, the host does delete but the confirmation window never goes away on it’s own.

[Tom Elliott]

Finally was able to get around to locating the issue on this. It has since been replicated and now I am certain this is solved.

Please update and let me know.

Thank you for reporting and sorry it took so long to figure out.

[x23piracy]

Hi,

i already described that issue earlier here: https://forums.fogproject.org/topic/7608/new-security-feature-cannot-delete-hosts

Regards X23

[Wayne Workman]

@x23piracy Sorry for overlooking that. When I realize two reports are the same, I cross-link them. Just didn’t notice this time.

[Tom Elliott]

@x23piracy I only called this one out because it was the latest one. Don’t think I just choose favorites. Is this now working properly for you as well?

[x23piracy]

I will update tomorrow and get back, no problem no worries all fine.

[x23piracy]

@Tom-Elliott all good now, problem solved.

Regards X23