periodic-ovb-1ctlr_1comp-featureset020-master fails tempest test_auto_allocate_network tempest.api.compute.images.test_images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Arx Cruz |
Bug Description
The periodic-
2019-03-26 04:18:06 | tempest.
2019-03-26 04:18:06 | Body: {"badRequest": {"message": "Unable to automatically allocate a network for project 34df197c8cc848c
2019-03-26 04:18:06 | tearDownClass (tempest.
2019-03-26 04:18:06 | testtools.
2019-03-26 04:18:06 | testtools.
[1] http://
[2] http://
Changed in tripleo: | |
milestone: | none → stein-rc1 |
tags: | removed: promotion-blocker |
Changed in tripleo: | |
status: | Triaged → Fix Released |
Changed in tripleo: | |
status: | Fix Released → In Progress |
related to https:/ /review. openstack. org/#/c/ 641368 ?
09:24 < ykarel> marios_|ruck, is fs020 failure known? 09:24 < ykarel> 1 tempest test is failing since tempestconf patch:- https:/ /review. openstack. org/#/c/ 641368/
09:28 < kopecmartin> ykarel|lunch, marios_|ruck if the test was skipped before, was it because microversions weren't set for compute? because that's what was added to python-tempestconf .. if that's the case, add those tests to blacklist