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.
VDSM is now configuring libvirtd upstart job, in RHEV-H we can configure it in the image, to avoid stopping libvirtd as sysv and restarting as upstart job on boot.
+++ This bug was initially created as a clone of Bug #694026 +++
Description of problem:
vdsm use to control libvirtd using System V init script,
as part of libvirtd upstart job, vdsm should move to control libvirtd using init upstart initctl.
--- Additional comment from danken on 2011-04-06 09:16:18 EDT ---
we should follow https://www.redhat.com/archives/libvir-list/2011-February/msg00789.html to disabled sysv init script and enable the upstart one.
I thought that you would not allow vdsm-specific configuration such as this before registration to rhev-m. If I knew that you would, we could have done this configuration on vdsm post script...
libvirtd upstart job is useful in general, nothing vdsm specific about it, but since vdsmd was using sysv initscript, we couldn't use it before.
How would your post script look like?
libvirt refused to make upstart their default in RHEL-6; I guess their reasoning could apply to rhevm-less rhevh.
Anyway, I guess the post script could be not very different from what we currently do on vdsmd startup. Hmmm, but we cannot use it in RHEL where libvirt version (and the location of the upstart script) may change in time.
start_libvirtd() {
local packaged installed target
local startout
packaged=`/bin/rpm -ql libvirt | /bin/grep libvirtd.upstart | \
/usr/bin/tail -1`
target=/etc/init/libvirtd.conf
installed=`/bin/readlink -f "$target"`
if [[ "$packaged" != "$installed" ]];
then
/bin/ln -sf "$packaged" "$target" || return 1
/sbin/initctl reload-configuration
fi
startout=`/sbin/initctl start libvirtd 2>&1`
if [[ "$?" -eq 0 || "$startout" =~ .*already\ running.* ]];
then
return 0
else
echo "$startout" >&2
return 1
fi
}
(In reply to comment #3)
> libvirt refused to make upstart their default in RHEL-6; I guess their
> reasoning could apply to rhevm-less rhevh.
Their reasoning is fine for RHEL-6 in general (it would be unexpected change for the users mid-release) but rhevh is a blackbox (also 6.x wasn't public yet) and I'm confident in using libvirtd upstart job there.
Actually in RHEV-H we must configure upstart job during image creation, vdsmd code in comment 3 will create dangling symlink on the running RHEV-H:
/etc/init/libvirtd.conf -> /usr/share/doc/libvirt-0.9.2/libvirtd.upstart
Files marked %doc are not installed in the RHEV-H image (%packages --excludedocs)
According to comment 16, verified this bug on rhev-hypervisor 6.2-0.14, have removed /etc/rc.d/init.d/libvirtd, and updated /etc/rc.d/init.d/vdsmd with libvirt things.
# grep -i start_libvirt /etc/init.d/vdsmd
start_libvirtd() {
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/RHBA-2011-1783.html