Bug 1193848
| Summary: | [REGENERATE PYTHON SDK] Element ovirtsdk.infrastructure.brokers.StorageDomain object has no attribute 'is_attached' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | David Caro <dcaroest> |
| Component: | ovirt-engine-sdk-python | Assignee: | Juan Hernández <juan.hernandez> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.0 | CC: | amureini, eedri, gklein, juan.hernandez, khakimi, lpeer, lsurette, mlipchuk, ncredi, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi |
| Target Milestone: | ovirt-3.6.0-rc3 | Keywords: | Automation |
| Target Release: | 3.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-sdk-python-3.6.0.0-0.1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-20 01:32:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Caro
2015-02-18 12:13:39 UTC
Maor, this sounds familiar from one of your recent patches. Please take a look? (In reply to Allon Mureinik from comment #1) > Maor, this sounds familiar from one of your recent patches. > Please take a look? The issue which you refer to is the importxx field, this is a different field (is_attached), which is also, not mandatory, and was only added recently. Just to be on the safe side, I've tried to add a new Storage Domain through REST and it worked. This is the request which I used which succeed: <storage_domain> <name>DataDomainRest</name> <type>data</type> <storage> <address>10.35.16.2</address> <type>nfs</type> <path>/export/images/rnd/maor/data3</path> </storage> <host> <name>pluto-vdsb.eng.lab.tlv.redhat.com</name> </host> <storage_format>v3</storage_format> </storage_domain> <storage_domain> <name>DataDomainRest</name> <type>data</type> <storage> <address>10.35.16.2</address> <type>nfs</type> <path>/export/images/rnd/maor/data3</path> </storage> <host> <name>pluto-vdsb.eng.lab.tlv.redhat.com</name> </host> <storage_format>v3</storage_format> </storage_domain> It looks like the SDK version was not compatible with the engine version, Juan, could it be that this is the origin of the problem? In order to support the "is_attached" property the SDKs need to be regenerated. This issue has been fixed in upstream version 3.6.0.0preview9 and will be available downstream with the first 3.6 build. [Ovirt SDK] in StorageDomain object missing "is_attached" and "import" fields thus our regression mix failed in build vt14: http://jenkins.qa.lab.tlv.redhat.com:8080/job/3.5-regression_mixed/84/consoleFull looking for: 23:41:57 2015-03-09 23:41:57,431 - MainThread - storagedomains - ERROR - Element '<ovirtsdk.infrastructure.brokers.StorageDomain object at 0x31ed490>' has no attribute 'is_attached' 23:41:57 2015-03-09 23:41:57,435 - MainThread - storagedomains - ERROR - Element '<ovirtsdk.infrastructure.brokers.StorageDomain object at 0x31ed490>' has no attribute 'import' Note that these missing attributes will be available when the SDKs are rebased using upstream version 3.5.2, and in order to do that the following bugs need to be approved: Rebase Python SDK to upstream 3.5.2 https://bugzilla.redhat.com/1196980 Rebase Java SDK to upstream 3.5.2 https://bugzilla.redhat.com/1196981 this bug has both 3.5.z & 3.6.0 flags, in bugzilla lang it means its a clone candidate from 3.6.0 to 3.5.z meaning it's pending a clone and wasn't fixed for 3.5.z. if this isn't the case, please fix flags accordingly, if it is the case, then please clone the bugs to 3.5.7 (3.5.6 was built already) This fix was included in release 3.5.2.1. I can't remove the rhevm-3.5.z flag. Allon, can you? (In reply to Juan Hernández from comment #10) > This fix was included in release 3.5.2.1. I can't remove the rhevm-3.5.z > flag. Allon, can you? Shouldn't this be closed current release then? No, this is a 3.6 bug. The bug that fixed the issue in 3.5 is bug 1196980, that is CLOSED ERRATA. (In reply to Juan Hernández from comment #12) > No, this is a 3.6 bug. The bug that fixed the issue in 3.5 is bug 1196980, > that is CLOSED ERRATA. The doc text and ref bug, do not include anything like this one. Can you point me to the bug tracking this fix for 3.5 oVirt\RHEV? The bug tracking this fix for 3.5 is bug 1196980. The Python SDK (and the Java SDK) is automatically generated from the metadata provided by the engine. We don't explicitly track each single change that re-generation introduces, instead we use generic bugs, like bug 1196980. |