Bug 1429021
| Summary: | When trying to move a template's disk via Python SDK, error message placeholder is not resolved | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | nicolas | ||||||
| Component: | Backend.Core | Assignee: | Benny Zlotnik <bzlotnik> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Natalie Gavrielov <ngavrilo> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.1.1 | CC: | amureini, bugs, juan.hernandez, omachace, ratamir, tnisan, ylavi | ||||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||||
| Target Release: | 4.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-12-20 11:02:37 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: |
|
||||||||
Created attachment 1264956 [details]
script to reproduce
Created attachment 1306883 [details] test script Verified with the attached script (pretty much the same as the script attached in comment 1). Builds used: ovirt-engine-4.2.0-0.0.master.20170725202023.git561151b.el7.centos.noarch vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64 This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Description of problem: I mistakenly tried to move a template's disk via Python SDK v. 4.1.1, which fairly threw an exception, the problem is that the exception message seems not to have a variable interpolated and the variable name is printed instead: [2017-03-03 20:42:03] Moving disk with ID ae6622bc-...-...-...-08df012c6bc2 to datastore XXX Traceback (most recent call last): [...] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot move Virtual Disk. The following disk(s) are not attached to any VM: ${diskAliases}.]". HTTP response code is 400. I guess ${diskAliases} should be interpolated and the real value should be shown. Version-Release number of selected component (if applicable): ovirt-engine-sdk-python ver. 4.1.1 How reproducible: Always