Created attachment 1314243 [details] vdsm.log Description of problem: [root@alma03 ~]# hosted-engine --set-shared-config fqdn someone.com --type he_conf Exception AttributeError: "'NoneType' object has no attribute 'dispatcher'" in <bound method _Server.__del__ of <vdsm.jsonrpcvdscli._Server object at 0x1ac0c90>> ignored [root@alma03 ~]# hosted-engine --get-shared-config fqdn --type he_conf fqdn : someone.com, type : he_conf Exception AttributeError: "'NoneType' object has no attribute 'dispatcher'" in <bound method _Server.__del__ of <vdsm.jsonrpcvdscli._Server object at 0x1908c90>> ignored Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.0-0.0.master.20170814052558.git066c94c.el7.centos.noarch ovirt-hosted-engine-ha-2.2.0-0.0.master.20170811094025.20170811094022.git1ef5937.el7.centos.noarch ovirt-host-deploy-1.7.0-0.0.master.20170720074349.gitd8609b1.el7.centos.noarch vdsm-yajsonrpc-4.20.2-74.git2be4775.el7.centos.noarch vdsm-4.20.2-74.git2be4775.el7.centos.x86_64 libvirt-client-3.2.0-14.el7_4.2.x86_64 libvirt-lock-sanlock-3.2.0-14.el7_4.2.x86_64 qemu-kvm-ev-2.6.0-28.el7.10.1.x86_64 How reproducible: 100% Steps to Reproduce: 1.Deploy SHE on using Ovirt on RHEL7.4 host. 2.Run "hosted-engine --get-shared-config fqdn --type he_conf" Actual results: Exception AttributeError: "'NoneType' object has no attribute 'dispatcher'" in <bound method _Server.__del__ of <vdsm.jsonrpcvdscli._Server object at 0x12b7c90>> ignored Expected results: No errors should happen. Additional info: vdsm log is attached.
Works for me, please test.
Works for me on these components: ovirt-hosted-engine-ha-2.2.0-0.0.master.20171128125909.20171128125907.gitfa5daa6.el7.centos.noarch ovirt-hosted-engine-setup-2.2.0-0.0.master.20171129192644.git440040c.el7.centos.noarch Deployed SHE over Gluster: alma04 ~]# hosted-engine --get-shared-config fqdn --type he_conf fqdn : myfqdn.at.somewhere.com, type : he_conf Moving to verified.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.