Bug 1023112 - Upgrade from VDSM image to base Node leaves broken VDSM configuration
Upgrade from VDSM image to base Node leaves broken VDSM configuration
Status: CLOSED NOTABUG
Product: oVirt
Classification: Community
Component: ovirt-node (Show other bugs)
4.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ryan Barry
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-24 12:02 EDT by Ryan Barry
Modified: 2013-10-25 10:04 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-25 10:04:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Barry 2013-10-24 12:02:41 EDT
Description of problem:
The removal of VDSM from the base ovirt-node image leaves a case where an upgrade can be performed to the next version of ovirt-node from an image without VDSM installed, and libvirtd.conf still configured for VDSM, so libvirtd fails to start.

Version-Release number of selected component (if applicable):
>3.0

How reproducible:
100%

Steps to Reproduce:
1. Install an ovirt-node image which includes VDSM.
2. Upgrade ovirt-node to an image which does not include VDSM.

Actual results:
libvirtd cannot start.
libvirtd log file complains that it cannot find /etc/pki/vdsm/certs/cacert.pem

Expected results:
libvirt works.
The upgrade process should leave a configured libvirtd.conf in place if the image includes VDSM (or other plugins in the future which configure libvirtd, but replace it with a base libvirtd.conf which works out of the box.

Additional info:
Comment 1 Fabian Deutsch 2013-10-25 10:04:50 EDT
Ryan,

we don't support this upgrade path (RHEV-H for RHEV to RHEV base image), so we can close this bug.
I did however opened bug 1023481 to track the creation of a sane libvirt config.

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