yahoo-eng-team team mailing list archive

[Arun Thulasi <arunuke@xxxxxxxxx>]

Public bug reported:

Hello All,

[This is more of a question than a bug]

I am running Fedora20/IceHouse/RDO. I have been using the
GroupAntiAffinityFilter to implement some affinity/anti-affinity rules.
I have GroupAntiAffinityFilter set in nova.conf for my filters and I
start my instances with the name of the group as a hint.

nova boot --flavor 1 --image <image-id> --hint group=test tstvm1.

Since the last couple of days, I have been getting failures with the
error that "instance group test could not be found". My current version
of nova client does not seem to have an option to set up instance groups
nor could I find any documentation from the most recent guide. Has
anyone hit this issue or been able to workaround this?

Looking through the stack, it appears that the failure happens since
there is no group. However, should nova be creating an instance group if
one is not available already?

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  instance groups and groupaffinityfilters

Status in OpenStack Compute (Nova):
  New

Bug description:
  Hello All,

  [This is more of a question than a bug]

  I am running Fedora20/IceHouse/RDO. I have been using the
  GroupAntiAffinityFilter to implement some affinity/anti-affinity
  rules. I have GroupAntiAffinityFilter set in nova.conf for my filters
  and I start my instances with the name of the group as a hint.

  nova boot --flavor 1 --image <image-id> --hint group=test tstvm1.

  Since the last couple of days, I have been getting failures with the
  error that "instance group test could not be found". My current
  version of nova client does not seem to have an option to set up
  instance groups nor could I find any documentation from the most
  recent guide. Has anyone hit this issue or been able to workaround
  this?

  Looking through the stack, it appears that the failure happens since
  there is no group. However, should nova be creating an instance group
  if one is not available already?

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