Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1434985

Summary: Nova Evacuation Failed while evacuating instance back to previously targeted host
Product: Red Hat OpenStack Reporter: Manisha Tripathy <manisha_tripathy>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: berrange, dasmith, eglynn, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-22 20:36:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Manisha Tripathy 2017-03-22 20:26:53 UTC
Description of problem:
With shared-storage backend, when I evacuate an instance first time, it works fine. But when I try to evacuate it back to its initial host it goes into error state giving permission denied error message. Details on checking the permissions on the directory /var/lib/nova/instances/<instance_id> are a follows
 
  Status	Permissions on Compute1	Permissions on Compute2
  Create Vm on compute1	qemu	               N/A
Compute1-Power On	qemu	               N/A
Compute-1 Power Off	qemu	               N/A
Evacuate to Compute2	qemu	               qemu
Power On Compute 1	root	               qemu
Power Off Compute 2	root	               qemu
Evacuate back to Compute 1-	root	       qemu (this is where it fails giving permission denied)
                                 

Version-Release number of selected component (if applicable):
RH0SP-10

How reproducible:
Every time

Steps to Reproduce:
Create the instance on shared storage (Ceph ephemeral), on Compute1
Verify the instance directory is created on compute1 in cd /var/lib/nova/instances/<instanceID>
Power off Compute1
Evacuate the instance to Compute2 (nova host-evacuate --target_host overcloud-compute-2.localdomain overcloud-compute-1.localdomain)
Verify the instance is running on Compute2 and the instance directory resides on Compute2 cd /var/lib/nova/instances/<instanceID>
Power on Compute1 and see that the instance directory is still there 
Power off Compute2
Evacuate the instance back to Compute1 (nova host-evacuate --target_host overcloud-compute-1.localdomain overcloud-compute-2.localdomain)
The instance comes up with ERROR state on overcloud-compute-1.localdomain

Comment 1 Manisha Tripathy 2017-03-22 20:36:37 UTC

*** This bug has been marked as a duplicate of bug 1434986 ***