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.
DescriptionMeital Bourvine
2014-02-24 14:56:37 UTC
Description of problem:
Stucked tuned service during host deploying
Version-Release number of selected component (if applicable):
ovirt-beta3
How reproducible:
80%
Steps to Reproduce:
Install rhevm and add a host.
Additional info (thanks to lbendar):
There is an error about "Existing lock /var/run/yum.pid"
you can track the process which caused that using pid. follow
instruction bellow:
{{{
ls -la /proc/$(cat /var/run/yum.pid)/fd | grep 'log$'
l-wx------. 1 root root 64 Feb 24 09:42 1 ->
/tmp/ovirt-host-deploy-20140220152021.log
}}}
and see ... it was caused by rhevm bootstrap ...
so we can take a look at log what happened:
{{{
[root@puma29 ~]# tail /tmp/ovirt-host-deploy-20140220152021.log
2014-02-20 15:21:14 DEBUG otopi.plugins.otopi.services.rhel
plugin.executeRaw:366 execute: ('/sbin/service', 'tuned', 'start'),
executable='None', cwd='None', env=None
2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel
plugin.executeRaw:383 execute-result: ('/sbin/service', 'tuned',
'start'), rc=0
2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel
plugin.execute:441 execute-output: ('/sbin/service', 'tuned', 'start')
stdout:
2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel
plugin.execute:446 execute-output: ('/sbin/service', 'tuned', 'start')
stderr:
2014-02-20 15:21:15 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned
plugin.executeRaw:366 execute: ('/usr/bin/tuned-adm', 'profile',
'virtual-host'), executable='None', cwd='None', env=None
}}}
and we are here again ... it leads to tuned service.
lets take a look at /var/log/tuned/tuned.log
I can not find anything interesting there
{{{
....
2014-02-20 15:10:35,110 INFO tuned: performing ktune conditional restart
....
}}}
Workaround:
modify: /usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/tune/tuned.py
def _misc(self):
# tuned-adm does not work if daemon is down!
self.services.state('tuned', True)
+ import time
+ time.sleep(5)
rc, stdout, stderr = self.execute(
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1069119
Description of problem: Stucked tuned service during host deploying Version-Release number of selected component (if applicable): ovirt-beta3 How reproducible: 80% Steps to Reproduce: Install rhevm and add a host. Additional info (thanks to lbendar): There is an error about "Existing lock /var/run/yum.pid" you can track the process which caused that using pid. follow instruction bellow: {{{ ls -la /proc/$(cat /var/run/yum.pid)/fd | grep 'log$' l-wx------. 1 root root 64 Feb 24 09:42 1 -> /tmp/ovirt-host-deploy-20140220152021.log }}} and see ... it was caused by rhevm bootstrap ... so we can take a look at log what happened: {{{ [root@puma29 ~]# tail /tmp/ovirt-host-deploy-20140220152021.log 2014-02-20 15:21:14 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/service', 'tuned', 'start'), executable='None', cwd='None', env=None 2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/service', 'tuned', 'start'), rc=0 2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/service', 'tuned', 'start') stdout: 2014-02-20 15:21:15 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/service', 'tuned', 'start') stderr: 2014-02-20 15:21:15 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.executeRaw:366 execute: ('/usr/bin/tuned-adm', 'profile', 'virtual-host'), executable='None', cwd='None', env=None }}} and we are here again ... it leads to tuned service. lets take a look at /var/log/tuned/tuned.log I can not find anything interesting there {{{ .... 2014-02-20 15:10:35,110 INFO tuned: performing ktune conditional restart .... }}} Workaround: modify: /usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/tune/tuned.py def _misc(self): # tuned-adm does not work if daemon is down! self.services.state('tuned', True) + import time + time.sleep(5) rc, stdout, stderr = self.execute( Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1069119