yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1658200

Title:
  Running tests via nosestests fails due to insufficient test isolation

Status in cloud-init:
  Fix Released

Bug description:
  I don't know if we care about this or not, since it involves a test
  harness other than tox.

  Attempting to run the unittests using nosetests (nosetets
  tests/unittests) will fail because the _set_mock_metadata method
  appears to only run once...so tests that expect non-default metadata
  (such as test_instance_level_keys_replace_project_level_keys) will
  fail if any prior test calls _set_mock_metadata().

  This can be avoided by calling httppretty.reset() before calling
  httppretty.register_uri(...).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1658200/+subscriptions