yahoo-eng-team team mailing list archive

[Matthew Treinish <mtreinish@xxxxxxxxxx>]

This is really a nova bug, and not a tempest bug.  Tempest exposes the
idempotent ids to enable tracking tests across renames. I don't feel
that the fact nova's cell job (which should be using config flags
instead of a giant regex anyway) isn't using this to identify tests in
its blacklist is justification for a revert. There are multiple options
here on the nova side to do this correctly, why does the fact this 1 job
doesn't use them warrant a revert?

** Changed in: tempest
   Importance: Critical => Undecided

** Changed in: tempest
       Status: In Progress => Opinion

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

Title:
  test_server_basic_ops rename in tempest is breaking cells job

Status in OpenStack Compute (nova):
  New
Status in tempest:
  Opinion

Bug description:
  Nova has a blacklist on tempest tests that won't work in the cells v1
  job, including:

  https://github.com/openstack/nova/blob/master/devstack/tempest-dsvm-
  cells-rc#L77

  With change https://review.openstack.org/#/c/296842/ there was a
  blacklisted test that was renamed so it's no longer skipped and the
  cells job is now failing on all nova changes.

  We can either revert the tempest change or update the blacklist in
  nova, but since tempest is branchless we'd have to backport that nova
  change to stable/mitaka, stable/liberty and stable/kilo.

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