https://review.opendev.org/c/openstack/tempest/+/770169 got merged.
** Changed in: tempest
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad
After discussion with Ghanshyam we can consider this bug done.
kopecmartin gmann: thanks .. btw, is this still in progress? i see bunch of
merged reviews, isn't it done already?
https://bugs.launchpad.net/tempest/+bug/1844568 14:22
openstack Launchpad bug 1844568 in tempest "[compute]
Seems like this is not fixed everywhere:
https://zuul.opendev.org/t/openstack/build/f1ae8eeb986a42e2b45d1a79e2e300e2
** Changed in: tempest
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
marking invalid from nova side as no fix needed on nova side for this.
** Changed in: nova
Status: Triaged => Invalid
--
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
tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest.test_qos_min_bw_allocation_basic,
which was enabled in the nova-next job this week:
https://review.opendev.org/#/c/697180/
is likely causing the spike in failures in the nova-next job. See this
failed job:
https://zuul
5 matches
Mail list logo