Bug 1844350
| Summary: | [CNV&RHV] Change of CPUs on OpenShift virtaulization VM from RHVM did not propagated back to OPenShift cluster | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Pavol Brilla <pbrilla> |
| Component: | BLL.Virt | Assignee: | Michal Skrivanek <michal.skrivanek> |
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4.0 | CC: | ahadas, bugs, ljelinko, lleistne, mperina, mtessun, pkliczew |
| Target Milestone: | --- | Flags: | mperina:
devel_ack?
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-08 19:10:49 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: | |||
*** This bug has been marked as a duplicate of bug 1843933 *** |
Description of problem: OpenShift VM connected to RHVM, changing of CPU cores number in rhevm from 2 to 1 was not propagated successfully Version-Release number of selected component (if applicable): How reproducible: 100 Steps to Reproduce: 1. Have kubevirt connection with RHVM 2. Edit VM - change core numbers 3. Save changes Actual results: RHVM takes changes but those are not propagated to OpenShift cluster, thus information about vm is stale Expected results: update openshift vm from rhvm Additional info: 2020-06-05 09:27:41,714+02 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-145) [24559276-4bee-4887-a03a-9caa84c33867] Running command: UpdateVmCommand internal: false. Entities affected : ID: b4012991-52bf-4142-8231-3696f19fc887 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2020-06-05 09:27:41,956+02 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-145) [7519f3c3] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2020-06-05 09:27:41,959+02 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-145) [7519f3c3] Updating RNG device of VM cirros-vm-notfromtemplate (b4012991-52bf-4142-8231-3696f19fc887) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='9659058d-af3f-404c-893e-31e508a2113d', vmId='b4012991-52bf-4142-8231-3696f19fc887'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='9659058d-af3f-404c-893e-31e508a2113d', vmId='b4012991-52bf-4142-8231-3696f19fc887'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. Potentional regression after discussion with Piotr