Bug 1443143

Summary:	Do not set tuned profile - leave whatever the guest has
Product:	[oVirt] ovirt-guest-agent	Reporter:	Yaniv Kaul <ykaul>
Component:	Core	Assignee:	Tomáš Golembiovský <tgolembi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Gonza <grafuls>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0.13	CC:	bugs, jbelka, tjelinek
Target Milestone:	ovirt-4.2.0	Keywords:	Improvement, Reopened
Target Release:	---	Flags:	tjelinek: ovirt-4.2? grafuls: testing_plan_complete- tjelinek: planning_ack? rule-engine: devel_ack+ pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:43:50 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 Yaniv Kaul 2017-04-18 15:05:54 UTC

Description of problem:
Atomic guest already has a suitable tuned profile. Don't set it during installation.

Comment 1 Tomas Jelinek 2017-04-26 08:11:26 UTC

This is done only during build time and wont affect the guest.

Closing as wont fix. If you think it affects the guest somehow, please feel free to reopen.

Comment 4 Jiri Belka 2017-12-07 10:17:38 UTC

ok, same as https://bugzilla.redhat.com/show_bug.cgi?id=1511924#c4

ovirt-guest-agent-common-1.0.14-3.el7ev.noarch.rpm

Comment 5 Sandro Bonazzola 2017-12-20 10:43:50 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.