Description of problem:
When updating oVirt from a prior release and setting the datacenter version to 3.5 there is no default disk profile added effectively preventing the creation of new disks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install oVirt engine 3.4.x
2. Upgrade oVirt engine to 3.5
3. Set datacenter version to 3.5
4. Add disk
Adding the disk fails with no error (cannot click OK), because there is no disk profile. Using a template however raises the error pointing to the root cause:
Cannot add disks: ACTION_TYPE_DISK_PROFILE_EMPTY
Disk is added, a default profile (unlimited) is used automatically if not existing.
I do not really know where to file the bug against, at the very least it is documentation or even RFE? Also, manually adding a default profile to every data domain solves the issue.
But there are already to documented cases of this pitfall in 3.5 on the users mailing list.
The operation of setting datacenter version is done through webadmin interface.
Moving to proper component.
I guess this is a duplicate bug of bz 1145241 ?
Indeed Seven, thanks. I realized after filing this BZ. Sandro or anyone - could you flag the dup to bz1145241 ?
At least this one got some more attention now.
*** This bug has been marked as a duplicate of bug 1145241 ***