Bug 1227902 - rhel-osp-director: [RFE] The launched instance doesn't migrate to live node(s) upon reboot, nor does it boot after the rebooted node resumes normal operation.
Summary: rhel-osp-director: [RFE] The launched instance doesn't migrate to live node(s...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Hugh Brock
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-03 18:22 UTC by Alexander Chuzhoy
Modified: 2019-09-09 15:21 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-30 07:56:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2015-06-03 18:22:32 UTC
openstack-nova: [RFE] The launched instance doesn't migrate to live node(s) upon reboot, nor does it boot after the rebooted node resumes normal operation.


Steps to reproduce:
1. Launch an instance on overcloud with 2 computes and working live migration.
2. Reboot the compute node on which the instance is running.
3. Check the status of the instance on both computes.

Result:
The instance isn't launched on the remaining compute.
After the rebooted compute resumes, the instance still won't launch.

Expected result:
The instance should either launch on another compute or resume on the rebooted one.

Comment 3 chris alfonso 2015-08-04 17:43:00 UTC
Would you mind verifying this is still the case. I believe we've fixed this.

Comment 6 Jaromir Coufal 2016-09-30 07:56:51 UTC
Please re-open if still valid.

Comment 7 Stephen Gordon 2016-10-01 03:05:23 UTC
(In reply to Alexander Chuzhoy from comment #0)
> openstack-nova: [RFE] The launched instance doesn't migrate to live node(s)
> upon reboot, nor does it boot after the rebooted node resumes normal
> operation.
> 
> 
> Steps to reproduce:
> 1. Launch an instance on overcloud with 2 computes and working live
> migration.
> 2. Reboot the compute node on which the instance is running.
> 3. Check the status of the instance on both computes.
> 
> Result:
> The instance isn't launched on the remaining compute.
> After the rebooted compute resumes, the instance still won't launch.
> 
> Expected result:
> The instance should either launch on another compute or resume on the
> rebooted one.

This is actually expected behaviour, the only thing that would be expected to work in this case would be evacuate. If you want to live migrate you need to initiate it while the host is still up.


Note You need to log in before you can comment on or make changes to this bug.