volume id is always none when getting retry parameter in scheduler

Bug #1765927 reported by TommyLike
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

This below is the scheduler log when trying to reschedule create volume requests.
```
Apr 21 17:23:53 ecs-ecff-0001 cinder-scheduler[1128]: ERROR cinder.scheduler.flo
ws.create_volume [None req-7062c0db-0037-464e-971d-0094724ee104 admin None] Fail
ed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;vol
ume:create: No valid backend was found. Exceeded max scheduling attempts 3 for v
olume None: NoValidBackend: No valid backend was found. Exceeded max scheduling
attempts 3 for volume None
Apr 21 17:23:53 ecs-ecff-0001 cinder-scheduler[1128]: DEBUG cinder.volume.flows.
common [None req-7062c0db-0037-464e-971d-0094724ee104 admin None] Setting Volume
 f865c458-cd0b-4f88-819a-01ec27b78d12 to error due to: No valid backend was foun
d. Exceeded max scheduling attempts 3 for volume None {{(pid=1128) error_out /op
t/stack/cinder/cinder/volume/flows/common.py:83}}
```

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.