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.
Bug 627661 - libvirtd fails to start in RHEV-H
Summary: libvirtd fails to start in RHEV-H
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 638986
TreeView+ depends on / blocked
 
Reported: 2010-08-26 15:39 UTC by Mike Burns
Modified: 2016-04-26 14:59 UTC (History)
16 users (show)

Fixed In Version: vdsm-4.9-19.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-19 15:09:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Burns 2010-08-26 15:39:25 UTC
Description of problem:
When booting RHEV-H on some hardware, libvirtd fails to start correctly.

This has been simulated on a virtual machine with an ide disk and a physical machine with a sata disk

from /var/log/messages:  Aug 26 11:41:10 localhost libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory

The failure of libvirtd to start causes ovirt-post to wait until a timeout is reached.  This causes a large number of messages in ovirt.log like:

Aug 26 11:41:10 Waiting for libvirt to finish initializing...

Version-Release number of selected component (if applicable):
RHEV-H 6.0-13

How reproducible:
Intermittent, always on some machines

Steps to Reproduce:
1. Boot RHEV-H iso
2.
3.  

Actual results:
On some hosts, libvirt fails

Expected results:
libvirts starts everywhere

Additional info:

Comment 1 Alan Pevec 2010-08-26 16:41:24 UTC
Could not find keytab file is just informational, we're not configuring libvirt for gssapi authentication.

Real root cause is:
stat("/etc/pki/CA/cacert.pem", 0x7fff2812a680) = -1 ENOENT (No such file or directory)

/etc/pki/CA/cacert.pem -> /etc/pki/vdsm/certs/cacert.pem

but /etc/pki/vdsm/certs/cacert.pem does not exist

Comment 3 Alan Pevec 2010-08-26 17:05:58 UTC
Workaround is to comment out line in /etc/sysconfig/libvirtd

LIBVIRTD_ARGS=--listen # by vdsm

Dan, why does vdsm need libvirt RPC, isn't it using local unix socket connection to libvirtd ?

Comment 4 Daniel Berrangé 2010-08-26 17:46:44 UTC
libvirtd only needs the --listen argument if someone is going to connect to it remotely over TCP/TLS. AFAIK, VDSM is always running locally using the UNIX domain socket, so this shouldn't be required.

Comment 6 Dan Kenigsberg 2010-08-27 08:38:17 UTC
(In reply to comment #4)
> libvirtd only needs the --listen argument if someone is going to connect to it
> remotely over TCP/TLS. AFAIK, VDSM is always running locally using the UNIX
> domain socket, so this shouldn't be required.

We have to --listen for migration, aren't we?

Comment 8 Daniel Berrangé 2010-08-27 11:11:56 UTC
> We have to --listen for migration, aren't we?

If using the P2P or TUNNELLED migration methods, then yes you need libvirtd to listen on TCP.


Note You need to log in before you can comment on or make changes to this bug.