Bug 1725390
| Summary: | ovirt-engine 4.3.5-2 fails to add disk/update OVF/deactivate SD on a storage domain which resides on a 4.1 compatibility level cluster: InvalidParameterException: Invalid parameter: 'DiskType=2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Avihai <aefrat> | ||||
| Component: | Core | Assignee: | shani <sleviim> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Avihai <aefrat> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 4.30.23 | CC: | bugs, nsoffer, sbonazzo, sleviim, tnisan | ||||
| Target Milestone: | ovirt-4.3.5 | Keywords: | Automation, Regression | ||||
| Target Release: | 4.30.24 | Flags: | sbonazzo:
ovirt-4.3?
sbonazzo: blocker? |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | vdsm-4.30.24 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause:
Failed to create a new disk for a VM over a cluster with a 4.1 compatibility.
Consequence:
The disk type is parsed as int instead of a string (due to a prior fix: Bug 1723873)
Fix:
Treat the disk type as a string
Result:
Creation succeeded.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-07-30 14:08:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Avihai
2019-06-30 11:21:12 UTC
This effect the following on a SD/VM/Disk that is created on 4.1 cluster: 1) creating disk floating or on VM fails 2) updating OVF fails 3) deactivating storage domain with OVF update fails Also ISCSI and Gluster disks/SD's on 4.1 cluster are effected. Moving to vdsm since this is vdsm regression in 4.3. Sandro, this is another blocker for 4.3.5 (regression introduced by the previous fix already included in 4.3.5). (In reply to Nir Soffer from comment #4) > Sandro, this is another blocker for 4.3.5 (regression introduced by the > previous > fix already included in 4.3.5). taken Verified at ovirt-engine 4.3.5.4/vdsm-4.30.24-2.el7ev.x86_64. Steps to Reproduce: 1. Create a DC+cluster on 4.1 compatibility level 2. Add NFS storage domain to that DC 3. Create VM 4. Add a disk to this VM Actual results: VM Disk addition succeeds. This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |