{"action":"created","issue":{"url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/16","repository_url":"https://api.github.com/repos/wefixit-AT/oVirtBackup","labels_url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/16/comments","events_url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/16/events","html_url":"https://github.com/wefixit-AT/oVirtBackup/issues/16","id":147819299,"number":16,"title":"Error message \"400 / Bad Request / Internal Engine Error\" when using backup.py on some VMs","user":{"login":"fthommen","id":279232,"avatar_url":"https://avatars.githubusercontent.com/u/279232?v=3","gravatar_id":"","url":"https://api.github.com/users/fthommen","html_url":"https://github.com/fthommen","followers_url":"https://api.github.com/users/fthommen/followers","following_url":"https://api.github.com/users/fthommen/following{/other_user}","gists_url":"https://api.github.com/users/fthommen/gists{/gist_id}","starred_url":"https://api.github.com/users/fthommen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fthommen/subscriptions","organizations_url":"https://api.github.com/users/fthommen/orgs","repos_url":"https://api.github.com/users/fthommen/repos","events_url":"https://api.github.com/users/fthommen/events{/privacy}","received_events_url":"https://api.github.com/users/fthommen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2016-04-12T17:25:25Z","updated_at":"2016-04-15T10:27:39Z","closed_at":null,"body":"When using backup.py on some(!) VMs, we get a \"Bad Request / Internal Engine Error\" during the cloning step:\r\n\r\n```\r\n$ ./backup.py -c ./config_testvm.cfg -d\r\nApr 12 10:50:05: Start backup for: testvm\r\nApr 12 10:50:24: Snapshot creation started ...\r\nApr 12 10:50:32: Snapshot operation(creation) in progress ...\r\nApr 12 10:50:41: Snapshot operation(creation) in progress ...\r\nApr 12 10:50:51: Snapshot operation(creation) in progress ...\r\nApr 12 10:51:00: Snapshot created\r\nApr 12 10:51:04: Clone into VM started ...\r\nApr 12 10:51:07: !!! Got a RequestError:\r\nstatus: 400\r\nreason: Bad Request\r\ndetail: Internal Engine Error\r\nApr 12 10:51:07: All backups done\r\nApr 12 10:51:07: Backup failured for:\r\nApr 12 10:51:07:   testvm\r\nApr 12 10:51:07: Some errors occured during the backup, please check the \r\nlog file\r\n$\r\n```\r\nThe used config file looks as follows:\r\n```\r\n$ cat config_testvm.cfg\r\n[config]\r\nvm_names: [\"testvm\"]\r\nvm_middle=_BACKUP\r\nsnapshot_description=Snapshot for backup script\r\nserver=https://our.ovirt.server/ovirt-engine/api\r\nusername=xxxx@xxxx\r\npassword=xxxx\r\nexport_domain=our_export_domain\r\ntimeout=5\r\ncluster_name=Default\r\nbackup_keep_count=3\r\ndry_run=False\r\nvm_name_max_length=32\r\nstorage_domain=our_storage_domain\r\nstorage_space_threshold=0.1\r\n$\r\n```\r\nThe same script with only the VM name changed in the configuration file works fine on other VMs.  When running the process for the failing VM manually through oVirt's admin webgui, then no error appears.\r\n\r\nThere is no obvious configuration difference between working and failing VMs.  The backup script is run directly on the oVirt server (`our.ovirt.server`).\r\n\r\nSystem and oVirt version information:\r\n```\r\n$ cat /etc/os-release \r\nNAME=\"CentOS Linux\"\r\nVERSION=\"7 (Core)\"\r\nID=\"centos\"\r\nID_LIKE=\"rhel fedora\"\r\nVERSION_ID=\"7\"\r\nPRETTY_NAME=\"CentOS Linux 7 (Core)\"\r\nANSI_COLOR=\"0;31\"\r\nCPE_NAME=\"cpe:/o:centos:centos:7\"\r\nHOME_URL=\"https://www.centos.org/\"\r\nBUG_REPORT_URL=\"https://bugs.centos.org/\"\r\n\r\nCENTOS_MANTISBT_PROJECT=\"CentOS-7\"\r\nCENTOS_MANTISBT_PROJECT_VERSION=\"7\"\r\nREDHAT_SUPPORT_PRODUCT=\"centos\"\r\nREDHAT_SUPPORT_PRODUCT_VERSION=\"7\"\r\n\r\n$ rpm -qa | grep ovirt\r\novirt-engine-restapi-3.5.6.2-1.el7.centos.noarch\r\novirt-hosted-engine-ha-1.2.8-1.el7.centos.noarch\r\novirt-release35-006-1.noarch\r\novirt-engine-setup-plugin-websocket-proxy-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-extensions-api-impl-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-sdk-python-3.6.3.0-1.el7.noarch\r\novirt-image-uploader-3.5.1-1.el7.centos.noarch\r\novirt-engine-backend-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-userportal-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-setup-base-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-jboss-as-7.1.1-1.el7.x86_64\r\novirt-engine-setup-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-dbscripts-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-cli-3.5.0.6-1.el7.centos.noarch\r\novirt-engine-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-setup-plugin-ovirt-engine-common-3.5.6.2-1.el7.centos.noarch\r\novirt-host-deploy-1.3.2-1.el7.centos.noarch\r\novirt-engine-setup-plugin-ovirt-engine-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-tools-3.5.6.2-1.el7.centos.noarch\r\novirt-iso-uploader-3.5.2-1.el7.centos.noarch\r\novirt-host-deploy-java-1.3.2-1.el7.centos.noarch\r\novirt-engine-webadmin-portal-3.5.6.2-1.el7.centos.noarch\r\nlibgovirt-0.3.3-1.el7.x86_64\r\novirt-hosted-engine-setup-1.2.6.1-1.el7.centos.noarch\r\novirt-engine-lib-3.5.6.2-1.el7.centos.noarch\r\novirt-engine-websocket-proxy-3.5.6.2-1.el7.centos.noarch\r\n$\r\n```\r\n\r\nIs there a way to further debug this kind of problem?  Like a `-vvv` option?  Looking at the ovirt-engine log on the server doesn't really help, as the relevant messages are mixed with hundreds of other messages being printed during normal operation of the oVirt engine.  In the concrete case it would e.g. be helpful to track down the concrete request (with data), which is failing.  We are currently using commit `394a8743fc59a9bb7b4a131b133aa992fb3a1f30` of oVirtBackup\r\n\r\n```\r\n$ git rev-parse HEAD\r\n394a8743fc59a9bb7b4a131b133aa992fb3a1f30\r\n$\r\n```\r\nThanks in advance\r\nFrank Thommen"},"comment":{"url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/comments/210406371","html_url":"https://github.com/wefixit-AT/oVirtBackup/issues/16#issuecomment-210406371","issue_url":"https://api.github.com/repos/wefixit-AT/oVirtBackup/issues/16","id":210406371,"user":{"login":"wefixit-AT","id":10380344,"avatar_url":"https://avatars.githubusercontent.com/u/10380344?v=3","gravatar_id":"","url":"https://api.github.com/users/wefixit-AT","html_url":"https://github.com/wefixit-AT","followers_url":"https://api.github.com/users/wefixit-AT/followers","following_url":"https://api.github.com/users/wefixit-AT/following{/other_user}","gists_url":"https://api.github.com/users/wefixit-AT/gists{/gist_id}","starred_url":"https://api.github.com/users/wefixit-AT/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wefixit-AT/subscriptions","organizations_url":"https://api.github.com/users/wefixit-AT/orgs","repos_url":"https://api.github.com/users/wefixit-AT/repos","events_url":"https://api.github.com/users/wefixit-AT/events{/privacy}","received_events_url":"https://api.github.com/users/wefixit-AT/received_events","type":"User","site_admin":false},"created_at":"2016-04-15T10:27:39Z","updated_at":"2016-04-15T10:27:39Z","body":"Yes you can send it to me, I will handle it with care and don't publish sensitive Information's and wipe it after we find the problem.\r\n\r\nCan you also create a empty third test VM with a disk of 1GB without a Operating System and run the backup on it. Maybe the VM has a strange problem.\r\n\r\nI had this before on a test network with a VM where I hit some official Bug's (again) which where already reported to oVirt. There was the problem that a snapshot was generate but the snapshot disk was, for unknown reasons, corrupt and the backup-script did the job but the export VM has no disks stored. During the debugging I saw that all the SDK methods report no errors but there where thousand entries in the engine.log which are not forwarded through the SDK.\r\n\r\nIn short, currently I'm sceptical since I switched from VMWare ESXi to oVirt, before I had never problems. But this is another story :-("}}