Trying to offline faulted drive results in stack trace

Description

Trying to offline a faulted drive in the GUI results in the following stack trace:

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 137, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1195, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 973, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/pool.py", line 1091, in offline
await self.middleware.call('disk.swaps_remove_disks', [disk])
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1238, in call
return await self._call(
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1195, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/service.py", line 42, in l_fn
return await fn(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 972, in nf
args, kwargs = clean_and_validate_args(args, kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 930, in clean_and_validate_args
value = attr.clean(args[args_index + i])
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 470, in clean
raise Error(self.name, 'Item#{0} is not valid per list types: {1}'.format(index, found))
middlewared.schema.Error: [disks] Item#0 is not valid per list types: [disk] null not allowed

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Bug Clerk December 15, 2020 at 12:56 PM

Bug Clerk December 15, 2020 at 12:54 PM

Colm Connolly December 12, 2020 at 9:07 PM

By way of an explanation, one of the SSDs in the SSD pool failed overnight. In the GUI, I tried to offline the failed drive. This provoked the stack trace above.

Colm Connolly December 12, 2020 at 8:44 PM

Debug. Taken after a reboot with the defective drive removed from the machine. I couldn't take a debug before reboot as the debug generation process got hung up on the read-only pool (named SSD).

Complete

Details

Assignee

Reporter

Affects versions

Priority

More fields

Katalon Platform

Created December 12, 2020 at 9:21 AM
Updated July 1, 2022 at 4:59 PM
Resolved December 15, 2020 at 12:57 PM