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:
libvirt fails to start on rhevh
2012-03-25 02:16:25.791+0000: 9008: error : virNetTLSContextCheckCertBasicConstraints:167 : The certificate /etc/pki/vdsm/certs/vdsmcert.pem basic constraints show a CA, but we need one for a server
Version-Release number of selected component (if applicable):
libvirt-0.9.10-5.el6.x86_64
rhev-hypervisor6-6.3-20120307.2.auto475
How reproducible:
Always (so far)
Steps to Reproduce:
1.install rhevh
2.login to TUI
Actual results:
Failed to establish libvirt connection
Expected results:
libvirt starts successfully
Additional info:
May be part of the reproducer:
Tried to register to rhevm-3.0.2_0001-2.el6 using add host flow.
which vdsm version is it?
Could you attach the relevant vdsmcert? I guess the problem is with whomever generated it.
Federico, please see if this is related to http://gerrit.ovirt.org/2657
Comment 2Douglas Schilling Landgraf
2012-05-04 02:19:30 UTC
*** Bug 815825 has been marked as a duplicate of this bug. ***
Comment 4Douglas Schilling Landgraf
2012-05-06 00:01:26 UTC
*** Bug 783388 has been marked as a duplicate of this bug. ***
Comment 8Douglas Schilling Landgraf
2012-05-11 14:26:20 UTC
Hi,
The libvirt upstart patch didn't work. There is a race condition, where the ca cert is renamed and the daemon is started. So, the scenario is, after the complete RHEV-H boot libvirt can be started *manually* (because the ca cert have been renamed).
Moving to ASSIGNED to work into a new solution to avoid the race.
Thanks
Douglas
Description of problem:
clean install rhev-h and configure network up,register rhev-h to rhevm,don't approve it to up,
then reboot rhev-h, there will be info about "Virtualzation hardware is unavailable" in login screen, after success to login,
"Failed to Establish Libvirt Connection" shows in the Status menu(Seen Screenshot of Status Menu.png), at the same time, failed to approve rhevh to up on rhevm side.
Version-Release number of selected component (if applicable):
rhevm-3.1.0-15.el6ev.noarch
rhevh-6.3-20120813.0.rhev31.el6_3.iso
How reproducible:
100%
Steps to Reproduce:
1. Clean install RHEVH
2. Configure network for RHEVH
3. Register to RHEVM 3.1 and don't approve it to up(please take care of the default port should be 443 now).
4. Reboot RHEVH
5. Approve RHEVH on RHEVM side.
Actual results:
After step 5, it failed to approve rhevh to up.
Expected results:
After step 5, it can approve rhevh to up successfully.
Additional info:
After failed to approve rhevh to up, if i reboot rhev-h again,does not encounter warning info in login screen and Status Menu, the rhev-h
can also be up.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-1508.html