Tempest fails with No valid backend was found. No weighed backends available

Bug #1959024 reported by Bas de Bruijne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Cinder Charm
New
Undecided
Unassigned

Bug Description

Tempest fails with:

---------------------------------------------------------------------
=============================
Failed 1 test - output below:
=============================

cinder_tempest_plugin.api.volume.test_create_from_image.VolumeAndVolumeTypeFromImageTest.test_create_from_image_with_volume_type_image_property
-----------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/snap/fcbtest/27/lib/python3.6/site-packages/cinder_tempest_plugin/api/volume/test_create_from_image.py", line 159, in test_create_from_image_with_volume_type_image_property
    volume = self.create_volume(**kwargs)
  File "/snap/fcbtest/27/lib/python3.6/site-packages/cinder_tempest_plugin/api/volume/base.py", line 97, in create_volume
    volume['id'], wait_until)
  File "/home/ubuntu/snap/fcbtest/27/.rally/verification/verifier-67ba3d3e-0f7b-48d3-893a-12c512bcc89b/repo/tempest/common/waiters.py", line 301, in wait_for_volume_resource_status
    resource_name=resource_name, resource_id=resource_id)
tempest.exceptions.VolumeResourceBuildErrorException: volume a3270807-ffaf-4a06-9c5a-80293db7bc58 failed to build and is in ERROR status
---------------------------------------------------------------------

From the cinder logs I can see:

---------------------------------------------------------------------
cinder/cinder-scheduler.log-2022-01-25 15:13:33.908 968321 WARNING cinder.scheduler.filter_scheduler [req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3 dcd9646580534f1598186f66c869fff1 ce9f21635a9f4e5d822f6d14338b5e8d - b574e1bc94af46e7a167516046150788 b574e1bc94af46e7a167516046150788] No weighed backend found for volume with properties: {'id': '7bb1eb3a-9021-43cb-afa5-813a237af276', 'name': 'vol-type-for-6e9266ff-a917-4dd5-aa4a-c36e59e7a2a6', 'description': 'Generic volume_type for test 6e9266ff-a917-4dd5-aa4a-c36e59e7a2a6', 'is_public': True, 'projects': [], 'extra_specs': {'storage_protocol': 'iSCSI', 'vendor_name': 'Open Source'}, 'qos_specs_id': None, 'created_at': '2022-01-25T15:13:23.000000', 'updated_at': None, 'deleted_at': None, 'deleted': False}
cinder/cinder-scheduler.log-2022-01-25 15:13:33.908 968321 INFO cinder.message.api [req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3 dcd9646580534f1598186f66c869fff1 ce9f21635a9f4e5d822f6d14338b5e8d - b574e1bc94af46e7a167516046150788 b574e1bc94af46e7a167516046150788] Creating message record for request_id = req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3
cinder/cinder-scheduler.log-2022-01-25 15:13:33.964 968321 ERROR cinder.scheduler.flows.create_volume [req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3 dcd9646580534f1598186f66c869fff1 ce9f21635a9f4e5d822f6d14338b5e8d - b574e1bc94af46e7a167516046150788 b574e1bc94af46e7a167516046150788] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available: cinder.exception.NoValidBackend: No valid backend was found. No weighed backends available
cinder/cinder-scheduler.log:2022-01-25 15:13:33.964 968321 DEBUG cinder.volume.flows.common [req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3 dcd9646580534f1598186f66c869fff1 ce9f21635a9f4e5d822f6d14338b5e8d - b574e1bc94af46e7a167516046150788 b574e1bc94af46e7a167516046150788] Setting Volume a3270807-ffaf-4a06-9c5a-80293db7bc58 to error due to: No valid backend was found. No weighed backends available error_out /usr/lib/python3/dist-packages/cinder/volume/flows/common.py:80
cinder/cinder-scheduler.log-2022-01-25 15:13:33.988 968321 DEBUG cinder.scheduler.manager [req-b23e76ef-2bc9-44a9-8b0d-0d46fd90abd3 dcd9646580534f1598186f66c869fff1 ce9f21635a9f4e5d822f6d14338b5e8d - b574e1bc94af46e7a167516046150788 b574e1bc94af46e7a167516046150788] Task 'cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create' (f6bc9863-c3b1-4f07-8eae-d391e447c936) transitioned into state 'SUCCESS' from state 'RUNNING' with result 'None' _task_receiver /usr/lib/python3/dist-packages/taskflow/listeners/logging.py:180
---------------------------------------------------------------------

Juju crashdump: https://drive.google.com/file/d/1Bta8P6jCm4lqv6xIDF8DSxZI64UhNSmh/view?usp=sharing

Tags: cdo-tempest
tags: added: cdo-tempest
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.