On Fri, May 17, 2019 at 4:10 PM <dan.midthun@gmail.com> wrote:
I am having a similar problem - upgrade from 4.2.7 to 4.3.3 ... My Data Center would not activate, and I was getting all sorts of errors on the UI. I ended up shutting down the existing engine VM using --shutdown-vm ... trying to restart it, the console would report that the volume could not be found and would not start. ugh.

so, ssh into another host of the cluster, same thing. grr.  --deploy goes through most of the settings up until what I am assuming is probably 4 on the UI ... errors at activating storage domain. I created a separate nfs share so that I can hopefully import my machines that are still limping along, since I havent rebooted the fileserver


2019-05-17 09:03:59,698-0400 DEBUG var changed: host "localhost" var "otopi_storage_domain_details" type "<type 'dict'>" value: "{
    "changed": false,
    "exception": "Traceback (most recent call last):\n  File \"/tmp/ansible_ovirt_storage_domain_payload_4b8QQJ/__main__.py\", line 664, in main\n    storage_domains_module.post_create_check(sd_id)\n  File \"/tmp/ansible_ovirt_storage_domain_payload_4b8QQJ/__main__.py\", line 526, in post_create_check\n    id=storage_domain.id,\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in add\n    return self._internal_add(storage_domain, headers, query, wait)\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n    return future.wait() if wait else future\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in wait\n    return self._code(response)\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in callback\n    self._check_fault(response)\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n    self._raise_error(response
 , body)\n  File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n    raise error\nError: Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400.\n",
    "failed": true,
    "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400."
}"


400 - Bad request?     

I's suggest to check engine.log on the bootstrap engine VM; unfortunately engine error responses are not always that explicit.
 
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2PW3IWTGGU6J3325VVHBGPIVBPWFUTNN/


--

Simone Tiraboschi

He / Him / His

Principal Software Engineer

Red Hat

stirabos@redhat.com   

@redhatjobs   redhatjobs @redhatjobs