[Yahoo-eng-team] [Bug 1226344] Re: instance-gc doesn't work on baremetal

2016-07-25 Thread Launchpad Bug Tracker
[Expired for tripleo because there has been no activity for 60 days.]

** Changed in: tripleo
   Status: Incomplete => Expired

-- 
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/1226344

Title:
  instance-gc doesn't work on baremetal

Status in OpenStack Compute (nova):
  Won't Fix
Status in tripleo:
  Expired

Bug description:
  Per bug 1226342 it's possible to get into a situation where a nova bm
  node has an instance uuid associated with it that doesn't exist
  anymore (it may be presented 'DELETED' or just completely gone).

  This should be detected and result in the node being forced off and
  deassociated from the instance uuid, in the same way a VM hypervisor
  kills rogue VM's, but for some reason it's not working.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1226344] Re: instance-gc doesn't work on baremetal

2014-09-04 Thread Sean Dague
baremetal deprecated

** Changed in: nova
   Status: Incomplete => Won't Fix

-- 
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/1226344

Title:
  instance-gc doesn't work on baremetal

Status in OpenStack Compute (Nova):
  Won't Fix
Status in tripleo - openstack on openstack:
  Triaged

Bug description:
  Per bug 1226342 it's possible to get into a situation where a nova bm
  node has an instance uuid associated with it that doesn't exist
  anymore (it may be presented 'DELETED' or just completely gone).

  This should be detected and result in the node being forced off and
  deassociated from the instance uuid, in the same way a VM hypervisor
  kills rogue VM's, but for some reason it's not working.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp