Bug 713196 - VDSM - Storage: getSpmStatus doesn't return latest info
Summary: VDSM - Storage: getSpmStatus doesn't return latest info
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: Daniel Paikov
URL:
Whiteboard: Storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-14 15:56 UTC by Daniel Paikov
Modified: 2013-07-04 07:45 UTC (History)
8 users (show)

Fixed In Version: vdsm-4.9-76.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:21:12 UTC
Target Upstream Version:

Attachments (Terms of Use)
vdsm.log (844.11 KB, application/x-gzip)
2011-06-14 15:56 UTC, Daniel Paikov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description Daniel Paikov 2011-06-14 15:56:54 UTC 
Created attachment 504712 [details]
vdsm.log

* Setup with at least 2 hosts.
* Reboot SPM host.
* Perform manual fencing (confirm host has been rebooted).
* RHEVM runs getSpmStatus on 2nd host - VDSM returns outdated ID/LVER.
* RHEVM runs fenceSpmStorage on 2nd host - VDSM refreshes the cache with new ID/LVER and fails fenceSpmStorage for having old ID/LVER.
Comment 2 Igor Lvovsky 2011-06-15 13:22:27 UTC 
http://gerrit.usersys.redhat.com/#change,588
Comment 4 Daniel Paikov 2011-07-03 12:23:59 UTC 
Checked on 4.9-79.
Comment 5 errata-xmlrpc 2011-12-06 07:21:12 UTC 
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/RHEA-2011-1782.html
Note You need to log in before you can comment on or make changes to this bug.