Created attachment 1091643 [details] engine and vdsm logs Description of problem: Unable to remove Data center Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a Data center using version 3.4 2. Create a Cluster (using version 3.6) 3. Add a host and a pair of storage domains (I used NFS) 4. Create a VM with a disk in each of the storage domains 5. Upgrade the Data center to version 3.6 6. Wait until the OVF stores are created on both storage domains 7. Remove the VM and its disks 8. Place both storage domains in maintenance mode, the non-master storage domain should also be detached 9. When the Data center reaches maintenance mode, attempt to remove it Actual results: The remove Data center operation fails Expected results: The data center should be removed Additional info: Find attached engine and vdsm logs
Tal, isn't this similar to a BZ you're already looking into?
Looks like Raz filed a similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1272110
Gilad, can you list the rpm versions for engine and vdsm you encountered this in please?
Allon, here are the RPM versions: Engine: ovirt-engine-extension-aaa-jdbc-1.0.1-1.el6ev.noarch ovirt-vmconsole-1.0.0-1.el6ev.noarch rhevm-setup-plugin-ovirt-engine-3.6.0.3-0.1.el6.noarch ovirt-engine-extension-aaa-ldap-setup-1.1.0-1.el6ev.noarch rhevm-setup-plugin-ovirt-engine-common-3.6.0.3-0.1.el6.noarch ovirt-host-deploy-1.4.0-1.el6ev.noarch ovirt-engine-extension-aaa-ldap-1.1.0-1.el6ev.noarch ovirt-host-deploy-java-1.4.0-1.el6ev.noarch ovirt-engine-extension-aaa-misc-1.0.0-2.el6ev.noarch ovirt-vmconsole-proxy-1.0.0-1.el6ev.noarch VDSM: vdsm-infra-4.17.10.1-0.el7ev.noarch vdsm-jsonrpc-4.17.10.1-0.el7ev.noarch vdsm-python-4.17.10.1-0.el7ev.noarch vdsm-yajsonrpc-4.17.10.1-0.el7ev.noarch vdsm-4.17.10.1-0.el7ev.noarch vdsm-cli-4.17.10.1-0.el7ev.noarch vdsm-xmlrpc-4.17.10.1-0.el7ev.noarch vdsm-hook-ethtool-options-4.17.10.1-0.el7ev.noarch
Indeed, same scenario at the bottom line, much longer way to reproduce, closing as duplicate *** This bug has been marked as a duplicate of bug 1272110 ***