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

Bug 1406345

Summary: VM in error state after evacuation
Product: Red Hat OpenStack Reporter: Mohammad Rizwan <myusuf>
Component: openstack-novaAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: berrange, dasmith, eglynn, jmelvin, kchamart, myusuf, panbalag, sbauza, sferdjao, sgordon, sknauss, srevivo, vromanso
Target Milestone: asyncKeywords: Unconfirmed
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1399227 Environment:
Last Closed: 2017-07-12 12:47:26 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:
Bug Depends On: 1399227    
Bug Blocks:    

Comment 5 Mohammad Rizwan 2017-01-11 08:54:08 UTC
Customer is not able to reproduce the issue at his side. He thinks that it is timing issue and not sure about what caused it.

I am trying to setup the environment and will try to reproduce. I don't think so it will be reproducible as customer didn't, but anyway I will give it a try.

Comment 6 Sahid Ferdjaoui 2017-01-11 09:25:04 UTC
(In reply to Mohammad Rizwan from comment #5)
> Customer is not able to reproduce the issue at his side. He thinks that it
> is timing issue and not sure about what caused it.
> 
> I am trying to setup the environment and will try to reproduce. I don't
> think so it will be reproducible as customer didn't, but anyway I will give
> it a try.

Yes I also think is a timing issue as I tried to explain in comment #4. If you can have a setup I could try to prepare a fix.

Thanks,
s.

Comment 7 Dave Maley 2017-01-18 20:08:46 UTC
(In reply to Mohammad Rizwan from comment #5)
> Customer is not able to reproduce the issue at his side. He thinks that it
> is timing issue and not sure about what caused it.
> 
> I am trying to setup the environment and will try to reproduce. I don't
> think so it will be reproducible as customer didn't, but anyway I will give
> it a try.

Any updates on setting up the reproduction env? Thanks!

Comment 8 Mohammad Rizwan 2017-02-15 09:36:44 UTC
I am also not able to reproduce it on my test environment.

see the resutl here :
http://pastebin.test.redhat.com/455654

Comment 9 Red Hat Bugzilla Rules Engine 2017-02-15 09:36:53 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 10 Sahid Ferdjaoui 2017-02-15 09:55:24 UTC
(In reply to Mohammad Rizwan from comment #8)
> I am also not able to reproduce it on my test environment.
> 
> see the resutl here :
> http://pastebin.test.redhat.com/455654

Hello Mohammad and thanks for your help. Can you try with more than 1 instance on the evacuated host, perhaps something like 15 instances.

Comment 11 Mohammad Rizwan 2017-02-15 11:25:48 UTC
I tried it with 10 instances due to lack of hardware. It got succeed.

Following is the result
http://pastebin.test.redhat.com/455696

Comment 12 Sahid Ferdjaoui 2017-02-16 13:53:50 UTC
(In reply to Mohammad Rizwan from comment #11)
> I tried it with 10 instances due to lack of hardware. It got succeed.
> 
> Following is the result
> http://pastebin.test.redhat.com/455696

On the description the only "step to reproduce" we can see is to evacuate a compute node. 
A first step would be to ensure your have the same setup (based on the sosreport shared) then probably asking customer more details about how to reproduce the case.

Comment 13 Mohammad Rizwan 2017-02-21 10:16:07 UTC
Customer was using ceph as cinder and glance backend. I created an environment based on this  information and reproduced.

I informed the customer about steps I followed for reproducer. He don't have any additional information on how it will be reproducible, Hence he agreed to close the case. The case has closed now.

Comment 14 awaugama 2017-09-07 19:12:37 UTC
Closed without a fix therefore QE won't automate