Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
File /etc/tune-profiles/active-profile is NULL on this build.
It is correct on the last version rhel-guest-image-7.0-20140314.0 and before.
Version-Release number of selected component (if applicable):
rhel-guest-image-7.0-20140320.1.x86_64.qcow2
How reproducible:
100%
Steps to Reproduce:
1. login booted image.
2.# cat /etc/tune-profiles/active-profile
#
Actual results:
NUll
Expected results:
virtual-guest
@Joey, yes we know that the paths have changed as below:
[ x"$guest_release" == x"7.0" ] &&if_tuned=`cat /etc/tuned/active_profile`
[ x"$guest_release" == x"6.5" ] &&if_tuned=`cat /etc/tune-profiles/active_profile`
And I check it as you do:
# tuned-adm active
No current active profile.
#
So, it's still a question.
Hi Joey,
I download the build again and checked it manually with nothing changed, yes it's normal, you can close this bug.
This bug is found by automation test, it turns out that this file was cleaned during automation, it's really strange cause I write nothing to change it, the only thing I do is to cat it as Comment 5. I run automation cases one by one manually, but can't reproduce it, but every time I run all the cases automatically, this file got cleaned.
Joey, would you please give us some suggestions to help locate this problem? Or, shall we just give this file read only permission?