Bug 1304347
| Summary: | Hosted-Engine: memory hotplug does not work for engine vm | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | BLL.HostedEngine | Assignee: | Andrej Krejcir <akrejcir> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.6.2.6 | CC: | alukiano, aperotti, bugs, dfediuck, mavital, mkalinin, rbarry, rhev-integ, usurse | ||||
| Target Milestone: | ovirt-4.3.1 | Keywords: | TestOnly, Triaged | ||||
| Target Release: | --- | Flags: | dfediuck:
ovirt-4.3?
rule-engine: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-03-01 10:17:49 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. oVirt 4.0 beta has been released, moving to RC milestone. oVirt 4.0 beta has been released, moving to RC milestone. Sounds like a RFE to me - in 4.0, HE is EL7 - so it can support hotplug. Can you test what the status is in 4.0? I believe we added some restriction to our code to make it work for 3.6, so it just prevent memory hotplug. I checked it under rhevm-4.0.0.2-0.1.el7ev.noarch, and I still can see error message: VDSM hosted_engine_1 command failed: unsupported configuration: maxMemory has to be specified when using memory devices. And HE VM memory has old value. See this bug also: bz#1523835. I believe we should combine them in one single d/s RFE and attach all customer cases to it. *** Bug 1523835 has been marked as a duplicate of this bug. *** Moving to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1523835. This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 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. |
Created attachment 1120721 [details] engine and vdsm logs Description of problem: Memory hotplug does not work for engine vm Message: Failed to hot set memory to VM HostedEngine. Underlying error message: unsupported configuration: maxMemory has to be specified when using memory devices Version-Release number of selected component (if applicable): rhevm-3.6.2.6-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Deploy hosted-engine 2. Enter to the engine and attach storage domain(to start auto-import process) 3. Update HE vm memory in hotplug mode Actual results: Hotplug memory failed on HE vm with error Expected results: Hotplug memory works for HE vm Additional info: if I remember correct, we support hotplug memory only for el7 guest, so we need to block hotplug memory for HE vm