yahoo-eng-team team mailing list archive

[Simon Li <1938400@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
The ironic instance will not be managed by nova if the service of itself is down，even the environment has multiple compute host and has up status service.

Steps to reproduce
===========
1. deploy multiple compute service with IronicDriver, call them svc1,svc2,svc3;
2. enroll a baremetal node in ironic, and the node enroll a hypervisor in nova, assume the host of hypervisor is svc1's.
3. create a running baremetal instance using nova compute on the baremetal node;
4. at this time, we can manage this ironic instance with nova, like power on/off;
5. make compute service of the svc1 to down;
6. now, we can't show hypervisor info of this node, and can't power on/off this instance.

Expected result
===========
We have 3 compute service, while the svc1 was down, the others should can manage this instance.

Actual result
===========
We can't do anything for this instance.

Environment
===========
all versions of nova.

Other
===========
This is because the IronicDriver flow the libvirt logical, but the ironic compute service only has the management duty, do not need to create instance like libvirt for virtual machine.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

- # Description
+ Description
+ ===========
  The ironic instance will not be managed by nova if the service of itself is down，even the environment has multiple compute host and has up status service.
  
- # Steps to reproduce
+ Steps to reproduce
+ ===========
  1. deploy multiple compute service with IronicDriver, call them svc1,svc2,svc3;
  2. enroll a baremetal node in ironic, and the node enroll a hypervisor in nova, assume the host of hypervisor is svc1's.
  3. create a running baremetal instance using nova compute on the baremetal node;
  4. at this time, we can manage this ironic instance with nova, like power on/off;
  5. make compute service of the svc1 to down;
  6. now, we can't show hypervisor info of this node, and can't power on/off this instance.
  
- # Expected result
+ Expected result
+ ===========
  We have 3 compute service, while the svc1 was down, the others should can manage this instance.
  
- # Actual result
+ Actual result
+ ===========
  We can't do anything for this instance.
  
- # Environment
+ Environment
+ ===========
  all versions of nova.
  
- # Other
+ Other
+ ===========
  This is because the IronicDriver flow the libvirt logical, but the ironic compute service only has the management duty, do not need to create instance like libvirt for virtual machine.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1938400

Title:
  compute service for ironic instance is not high availability

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  The ironic instance will not be managed by nova if the service of itself is down，even the environment has multiple compute host and has up status service.

  Steps to reproduce
  ===========
  1. deploy multiple compute service with IronicDriver, call them svc1,svc2,svc3;
  2. enroll a baremetal node in ironic, and the node enroll a hypervisor in nova, assume the host of hypervisor is svc1's.
  3. create a running baremetal instance using nova compute on the baremetal node;
  4. at this time, we can manage this ironic instance with nova, like power on/off;
  5. make compute service of the svc1 to down;
  6. now, we can't show hypervisor info of this node, and can't power on/off this instance.

  Expected result
  ===========
  We have 3 compute service, while the svc1 was down, the others should can manage this instance.

  Actual result
  ===========
  We can't do anything for this instance.

  Environment
  ===========
  all versions of nova.

  Other
  ===========
  This is because the IronicDriver flow the libvirt logical, but the ironic compute service only has the management duty, do not need to create instance like libvirt for virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1938400/+subscriptions