+++ This bug was initially created as a clone of Bug #1258097 +++ 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): Any How reproducible: Always Steps to Reproduce: 1. Create disk with alias or description of 250-300 ascii characters (Vdsm does not support non-ascii alias and description) Actual results: Disk is created on storage, but metadata is truncated and invalid. Expected results: Disk should not be created, and MetadataOverflowError should be returned to engine. Additional info: 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.
Tal, are we still waiting for anything for the 3.6 patch?
Nope, all is merged 3.6 as well as 3.5.z
To verify: 1. Create a storage domain (two scenarios - file and block). 2. Create a disk on that domain with alias and description of specific length (see the doc text for the different cases). 3. Take it down to maintenance and destroy it. 4. Import the storage domain. 5. Register the disk you previously created (http://www.ovirt.org/Features/ImportStorageDomain#Register_an_unregistered_disk). 6. Verify that the disk's alias and description are as expected, i.e. restored fully if they fit or cut if they overflow the max metadata DiskDescription length (210 bytes). Another test can be to follow only steps 1 and 2, and then verify that the disk metadata "DiskDescription" field is a complete and legal json string, i.e.: DiskDescription={...} Note that using too long disk alias/description might fail according to BZ 1280358, so use shorter names to avoid that issue.
both test passed. checked on engine version: 3.6.0.3-0.1.el6
Since oVirt 3.6.0 has been released, moving from verified to closed current release.