Description of problem: when user creates a geo rep session from CLI and trying to sync it to UI results in failure. Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0.master.20150203062303.git783b38a.el6.noarch How reproducible: Always. Steps to Reproduce: 1. Create a geo replication session from cli. 2. Now click on the sync button which is under the Geo-replication tab. 3. Actual results: It throws an error saying "Error while executing action: VAR_TYPE_GLUSTER_GEOREP_SESSION. General command validation failure. Expected results: User should be able to sync the session and view it in UI. Additional info:
Created attachment 990424 [details] Attaching the screenshot for the failure when user tries to sync the session
Log files can be found in the link below. http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1191472/ I see a null pointer exception in the engine logs.
I looked into this issue and could see the following lines in the engine.log: 2015-02-21 04:45:13,075 ERROR [org.ovirt.engine.core.bll.gluster.RefreshGeoRepSessionsCommand] (ajp--127.0.0.1-8702-8) [7680cca5] Error during CanDoActionFailure.: java.lang.NullPointerException at org.ovirt.engine.core.bll.gluster.GlusterCommandBase.canDoAction(GlusterCommandBase.java:107) [bll.jar:] at org.ovirt.engine.core.bll.gluster.RefreshGeoRepSessionsCommand.canDoAction(RefreshGeoRepSessionsCommand.java:33) [bll.jar:] This has been addressed to, in the patch : http://gerrit.ovirt.org/#/c/36938/ And I also see the engine version to be : 3.6.00.0.master.20150203062303.git783b38a.el6 And I assume from this, that this was built on 03/02/2015. But the above mentioned patch was merged on 05/02/2015. Kindly update your setup and try once.
Verified and works fine with ovirt-engine-3.6.0-0.0.master.20150219124503.gitafae793.el6.noarch Able to sync the gee-rep session to UI. As mentioned in comment 3 it was a problem with setup i.e engine was not updated, after upgrading the engine i do not see this issue.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.