new api endpoint to be used for recordsize choices for webUI

Description

It was found that middlewared was incorrectly handling zfs dataset recordsizes. This has been fixed in the backend but also requires front-end changes. Currently, there is a drop-down box that the webUI displays. I'm attaching a screenshot of where I'm talking about (sorry, don't know how else to describe it) The "Record Size" drop-down needs to call pool.dataset.recordsize_choices.

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk May 4, 2022 at 11:37 AM

Bug Clerk May 4, 2022 at 11:34 AM

Bug Clerk May 3, 2022 at 3:53 PM

Caleb April 29, 2022 at 5:50 PM

okay since we're using openZFS now, we can use the "pool.dataset.recordsize_choices" endpoint for zvols too. Both datasets and zvols should give a warning to the user if they choose a size smaller than `pool.dataset.recommended_zvol_blocksize`.

Zvols blocksizes should default to lower values (pool.dataset.recommended_zvol_blocksize) while datasets can be whatever the end-user chooses so long as it's not lower than `pool.dataset.recommended_zvol_blocksize`.

Ievgen Stepanovych April 27, 2022 at 5:27 PM

Actually will need confirmation on this, since currently we use a different set of static values for zvols.

Complete

Details

Assignee

Reporter

Labels

Time remaining

0m

Components

Priority

Katalon Platform

Created April 8, 2022 at 12:04 PM
Updated July 1, 2022 at 5:57 PM
Resolved May 5, 2022 at 8:42 AM