Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1482484

Summary: Cpu Shares filed doesn't applied on next boot in case of update running VM
Product: [oVirt] ovirt-engine Reporter: Shira Maximov <mshira>
Component: BLL.VirtAssignee: bugs <bugs>
Status: CLOSED DEFERRED QA Contact: Shira Maximov <mshira>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, rbarry, tjelinek
Target Milestone: ---Keywords: Reopened
Target Release: ---Flags: rbarry: ovirt-4.5?
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: 2020-04-01 14:47:03 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:
Bug Depends On: 1484023    
Bug Blocks:    

Description Shira Maximov 2017-08-17 11:51:46 UTC
Description of problem:
Cpu Shares filed  doesn't applied on next boot  in case of update running vm

Version-Release number of selected component (if applicable):
Software version:4.2.0-0.0.master.20170813134654.gitaee967b.el7.centos


How reproducible:
100%

Steps to Reproduce:
1. Update Cpu Shares when VM is running 
2. Stop the VM and start the vm
3. Check the Cpu Shares value.

Actual results:


Expected results:


Additional info:

Comment 1 Michal Skrivanek 2017-08-23 12:24:09 UTC
it is quite likely the same problem

*** This bug has been marked as a duplicate of bug 1484023 ***

Comment 2 Shira Maximov 2017-09-07 05:26:41 UTC
This bug has a different issue then bug 1484023

Comment 3 Tomas Jelinek 2017-09-07 08:39:02 UTC
right, this is a different issue. The problem is that it is not added to the ovf. But it is not a regression, it has never been added there.

Comment 4 Ryan Barry 2019-01-21 14:53:59 UTC
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both

Comment 5 Michal Skrivanek 2020-03-18 15:46:38 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 6 Michal Skrivanek 2020-03-18 15:51:24 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 7 Michal Skrivanek 2020-04-01 14:47:03 UTC
Closing old bug. Please reopen if still relevant/you want to work on it.