Red Hat Bugzilla – Bug 1280337
Alias and Description maximum size should be restricted
Last modified: 2015-11-11 09:37:31 EST
Description of problem:
Disk alias maximum size is 255 characters, and description is 500 characters.
These values are stored in disk metadata in the shared storage since ovirt
3.5. However, on block storage we have only about 250 bytes free.
When entering long values into these fields, the disk metadata is truncated
silently. The truncated data may become invalid, failing various operations
with the disk, and the alias and description becomes unreadable.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create disk with alias or description of 250-300 ascii characters
(Vdsm does not support non-ascii alias and description)
Disk is created on storage, but metadata is truncated and invalid.
Disk should not be created, and MetadataOverflowError should be returned to engine.
This porblem exists since first vdsm version, but it became a bigger problem
since ovirt 3.5 since disk alias is stored now in the disk metadata on
the shared storage.
There is a mismatch between the ovirt-engine database size limits to the size
of disk metadata. In storage domain format 3, we cannot store the full disk
alias and description in the shared storage.
This issue should be fixed both in engine (to support older vdsm versions) and
in vdsm (to support older engines). This bug is only about the vdsm side.
The engine side bug is tracked in a separate bug.
This BZ was created for the engine side of the bug.