Bug #52932
[rbd_support] pool removal can wedge the task queue
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
mgr[rbd_support] Failed to locate pool cbp-test-5f9430172d174118a85c22581a8f319 mgr[rbd_support] execute_task: [errno 2] error opening pool 'b'cbp-test-5f9430172d174118a85c22581a8f319'' mgr[rbd_support] Fatal runtime error: local variable 'ioctx' referenced before assignment Traceback (most recent call last): File "/usr/share/ceph/mgr/rbd_support/task.py", line 351, in execute_task task.refs[TASK_REF_POOL_NAMESPACE])) as ioctx: File "/usr/lib64/python3.6/contextlib.py", line 81, in __enter__ return next(self.gen) File "/usr/share/ceph/mgr/rbd_support/task.py", line 190, in open_ioctx with self.module.rados.open_ioctx(spec[0]) as ioctx: File "rados.pyx", line 533, in rados.requires.wrapper.validate_func File "rados.pyx", line 1220, in rados.Rados.open_ioctx rados.ObjectNotFound: [errno 2] error opening pool 'b'cbp-test-5f9430172d174118a85c22581a8f319''
Related issues
History
#1 Updated by Ilya Dryomov over 1 year ago
- Duplicated by Bug #58062: RBD tasks will stop if a pool is deleted, blocking further queue added
#2 Updated by Ilya Dryomov over 1 year ago
- Priority changed from Normal to High
- Backport changed from octopus,pacific to pacific,quincy
#3 Updated by Ilya Dryomov over 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 49036
#4 Updated by Ilya Dryomov over 1 year ago
- Status changed from Fix Under Review to Pending Backport
#5 Updated by Backport Bot over 1 year ago
- Copied to Backport #58084: pacific: [rbd_support] pool removal can wedge the task queue added
#6 Updated by Backport Bot over 1 year ago
- Copied to Backport #58085: quincy: [rbd_support] pool removal can wedge the task queue added
#7 Updated by Backport Bot over 1 year ago
- Tags set to backport_processed
#8 Updated by Backport Bot about 1 year ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".