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 809094 - [vdsm][bootstrap] CA for vdsmcert.pem isn't downloaded from rhevm, symlink to vdsmcert.pem is used instead
Summary: [vdsm][bootstrap] CA for vdsmcert.pem isn't downloaded from rhevm, symlink to...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Federico Simoncelli
QA Contact: Jakub Libosvar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-02 13:19 UTC by Jakub Libosvar
Modified: 2012-04-03 10:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-03 10:50:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Bootstrap log (26.41 KB, text/x-log)
2012-04-02 13:19 UTC, Jakub Libosvar
no flags Details

Description Jakub Libosvar 2012-04-02 13:19:26 UTC
Created attachment 574503 [details]
Bootstrap log

Description of problem:
After host is added to rhevm setup and ssl is used, there is no CA for vdsmcert on host:
[root@srh-03 certs]# ll /etc/pki/vdsm/certs/
total 4
lrwxrwxrwx. 1 root root   32 Apr  2 14:48 cacert.pem -> /etc/pki/vdsm/certs/vdsmcert.pem
-r--r--r--. 1 vdsm kvm  3581 Apr  2 14:49 vdsmcert.pem

As a consequence libvirt cannot create socket with TLS. I think cacert.pem is supposed to be a CA for vdsmcert.pem cause when ca.crt is downloaded from rhevm and cacert is replaced with that, libvirt starts. This is reproducible only on RHEL 6.3, on 6.2 cacert.pem is correct.

Version-Release number of selected component (if applicable):
ovirt-engine-3.1.0_0001-3.el6.x86_64
vdsm-4.9.6-4.5.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have rhel6.3 host
2. Add host to rhevm setup
  
Actual results:
Libvirt cannot create socket due to missing CA

Expected results:
CA is correctly downloaded from rhevm and libvirt starts

Additional info:
I don't know where the symlink comes from - I tried to catch links created by _linkOrPersist method but no symlink cacert.pem -> vdsmcert.pem was created there. Attaching bootstrap log.

Comment 3 Federico Simoncelli 2012-04-03 10:17:58 UTC
For some time vdsm was creating a symlink (in vdsm-gencerts.sh) cacert.pem -> vdsmcert.pem. Since bc93adf (Use certtool to generate the certificates) it's not doing it anymore. Could you remove the link and try again with a newer vdsm version? Thanks.

Comment 4 Jakub Libosvar 2012-04-03 10:50:38 UTC
vdsm-bootstrap-4.9.6-4.5.noarch fixes the issue. Closing.


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