yahoo-eng-team team mailing list archive

[Gábor Antal <antal@xxxxxxxxxxxxxxx>]

Public bug reported:

As a notification transformation guideline in [1] explains that each
called test in test_instance_action should ensure that instance is left
in ACTIVE state after a notification test. However currently it is not
ensured, thus some of the test does not even care about it (like
suspend, pause actions).

This can cause problems, which can be seen at [2]. In the future, we
should ensure that after a test, the instance is in active state.

[1]: https://github.com/openstack/nova/blob/39cd54091747723a392dc33a2b5d6f5a28b537a7/nova/tests/functional/notification_sample_tests/test_instance.py#L57
[2]: https://review.openstack.org/#/c/396225/21

** Affects: nova
     Importance: Undecided
     Assignee: Gábor Antal (gabor.antal)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Gábor Antal (gabor.antal)

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

Title:
  Instances are not left in active state after a notification test

Status in OpenStack Compute (nova):
  New

Bug description:
  As a notification transformation guideline in [1] explains that each
  called test in test_instance_action should ensure that instance is
  left in ACTIVE state after a notification test. However currently it
  is not ensured, thus some of the test does not even care about it
  (like suspend, pause actions).

  This can cause problems, which can be seen at [2]. In the future, we
  should ensure that after a test, the instance is in active state.

  [1]: https://github.com/openstack/nova/blob/39cd54091747723a392dc33a2b5d6f5a28b537a7/nova/tests/functional/notification_sample_tests/test_instance.py#L57
  [2]: https://review.openstack.org/#/c/396225/21

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