Bug 1408577
Summary: | Update vm pool via REST API fails because vm.vmStatic.maxMemorySizeMb is None | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | sefi litmanovich <slitmano> |
Component: | BLL.Virt | Assignee: | Arik <ahadas> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sefi litmanovich <slitmano> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | bugs, gklein, slitmano |
Target Milestone: | ovirt-4.1.0-beta | Keywords: | AutomationBlocker, Regression |
Target Release: | 4.1.0.2 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: blocker+ rule-engine: planning_ack+ ahadas: devel_ack+ mavital: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-01 14:43:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sefi litmanovich
2016-12-25 09:18:29 UTC
Sefi - if the bug is due to above issue and the patch is already merged into master - you can easily validate it and see if this bug is still relevant, no? Tried it again in ovirt-engine-4.1.0-0.3.beta2.el7.noarch, still happening. So maybe the fix didn't make it to that build yet. I understand it's the same issue as the bug I mentioned, but this is another 'symptom' so I figured it's better to document, but if this bug isn't needed we can close as duplicate or something. In any case, it's still exist on this build. (In reply to sefi litmanovich from comment #2) > Tried it again in ovirt-engine-4.1.0-0.3.beta2.el7.noarch, still happening. > So maybe the fix didn't make it to that build yet. > I understand it's the same issue as the bug I mentioned, but this is another > 'symptom' so I figured it's better to document, but if this bug isn't needed > we can close as duplicate or something. > In any case, it's still exist on this build. Correction - looking at the patch on the the other bug, I see the fix was specific to import flow. So in fact the symptom in this bug won't be fixed on that patch. I also guess that there probably other bugs touching this maxMemorySizeMb value. This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Verified with ovirt-4.1.0-0.4.master.20170116141310.gita30debd.el7.centos according to description. |