Created attachment 1153807 [details] hosted engine setup log Description of problem: Hosted engine deploy failed with: 2016-05-04 11:56:52 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 1283, in _misc self._spmStart() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 1026, in _spmStart domVersion=version, File "/usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py", line 168, in _callMethod return response.success(**resp.result) TypeError: success() argument after ** must be a mapping, not str Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.0.0-0.0.master.20160503103744.gite1f03e3.el7.centos.noarch vdsm-4.17.999-1036.git19a27af.el7.centos.noarch How reproducible: Always Steps to Reproduce: 1. Deploy HE 2. 3. Actual results: Deployment failed with above error Expected results: Deployment succeeds without any errors Additional info: we have check under _callMethod elif isinstance(resp.result, six.text_type): return response.success(resp.result) but six.text_type connect only to unicode strings, I believe we just need to change it to six.string_types
I assume it's a regression? An automation blocker?
Artyom - if you've fixed it (kudos!) and the patch is merged, why is the bug on NEW? Can probably be verified and CLOSED-UPSTREAM.
I was sure we have some automation for this purpose, correct me if I wrong, so it must be moved to the POST, when the patch posted and to the MODIFIED when the patch merged.
(In reply to Artyom from comment #3) > I was sure we have some automation for this purpose, correct me if I wrong, > so it must be moved to the POST, when the patch posted and to the MODIFIED > when the patch merged. Eyal?
oVirt 4.0 beta has been released, moving to RC milestone.
We don't enforce hooks for moving statues or enforcing bug-url on master branch. This will be enabled once we branch 4.0 branch and will work on 3.6 and 4.0 branches. usually master is too latest/greatest and enabling hooks that enforce validation might cause too much overhead, if we want to change that policy we need to raise it on devel and see what are the pro/cons.
Verified on ovirt-hosted-engine-setup-2.0.0-1.el7ev.noarch
oVirt 4.0.0 has been released, closing current release.