Bug 1080931
Summary: | vdsm libvirt and sanlock daemons need to be restarted after upgrading to sanlock 2.8 | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Federico Simoncelli <fsimonce> | |
Component: | vdsm | Assignee: | Federico Simoncelli <fsimonce> | |
Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.4.0 | CC: | amureini, bazulay, bmr, cluster-maint, fsimonce, iheim, jbiddle, lbopf, lpeer, michele, scohen, teigland, yeylon | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | 3.4.0 | Flags: | amureini:
Triaged+
|
|
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | storage | |||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Previously, a package update would lead to version errors in the sanlock command, because the daemon cannot be stopped while in use. Now, the documentation recommends restarting the host to ensure all updates are correctly applied.
|
Story Points: | --- | |
Clone Of: | 1054902 | |||
: | 1084946 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-09 13:29:50 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1054902 | |||
Bug Blocks: | 1084946 |
Comment 1
Federico Simoncelli
2014-03-26 10:50:45 UTC
This is a doc-only bug. Action items: 1. docs team should provide the doc-text as per the flag. 2. QA should verify the procedure in comment 1 works correctly. After upgrading sanlock from 2.6 to 2.8 using 'yum update' command, I restarted sanlock, libvirtd and vdsmd (while host was in maintenance) and activate the host in RHEVM, it went fine Tested using a RHEL host with: vdsm-4.13.2-0.7.el6ev.x86_64 (RHEV3.3-is33) libvirt-0.10.2-29.el6_5.7.x86_64 Upgraded sanlock from sanlock-2.6-2.el6.x86_64 to sanlock-2.8-1.el6.x86_64 Allon, we need to change the documentation: Restart order is important, need to perform the following: - put host to maintenance in RHEVM - yum update - restart sanlock - restart libvirtd - restart vdsmd - activate the host in RHEVM Jodi, I've update the suggested doctext as per Elad's comment 5. Please advise if this is doable for 3.4, or if you need any additional information. Hi Allon The doc text field is for the inclusion of release notes and errata. I've raised a separate bug against the guides component for your request. https://bugzilla.redhat.com/show_bug.cgi?id=1091762 I've fixed it - I went with your suggestion of just changing it to tell customers to restart after updating. Much simpler. 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-2014-0504.html |