Description of problem: Cannot switch host from Json RPC to XML RPC, the edit host dialog is stuck after pressing OK Version-Release number of selected component (if applicable): rhevm-3.6.0-0.11.master.el6.noarch vdsm-4.17.3-1.el7ev.noarch Steps to Reproduce: 1. Edit host and remove the mark from advance parameters > use JSON protocol > OK
Created attachment 1066228 [details] engine, vdsm and supervdsm logs
You shouldn't move hosts to xmlrpc in cluster level 3.6 (I think we have a bug in order to prevent that from being enabled in the UI). However, it shouldn't get stuck. Piotr - can you take a look and understand why it is stuck? In the meantime, it would be good to cover the other bug and just disable it...
Sure, will change it.
Please check latest master or 3.6. I tested both and after changing protocol I can see that it works. Host edit dialog is a bit to slow but a host is properly updated.
I am closing this bug as "not a bug". Please reopen if you notice the issue again.
I'd rather see the BZ to be closed as CURRENTRELEASE - based on c#4 it works, current version doesn't even offer that change on 3.6 Cluster - so something changed.
Pavel, what's working is that it isn't stuck as Meni said. However, you still won't be able to switch to xmlrpc. So the bug wasn't fixed, as it wasn't a bug. Do you think it should be back on notabug?
It was stuck as Meni said in the time he tested it. Since then someone change the code, thus I am voting for using proper status from https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status (I also think UPSTREAM doesn't make sense here).
Just making sure you're aware that you still won't be able to switch protocols in 3.6. By declaring this is fixed, someone might think it is possible.