Bug 767182 - VDSM - Storage: Bad output when running spmStart while another host is already SPM
Summary: VDSM - Storage: Bad output when running spmStart while another host is alread...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: ---
: 3.3.4
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 13:57 UTC by Daniel Paikov
Modified: 2016-02-10 16:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-11 21:58:25 UTC
oVirt Team: Storage

Attachments (Terms of Use)
vdsm.log (340.63 KB, application/x-gzip)
2011-12-13 13:58 UTC, Daniel Paikov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Daniel Paikov 2011-12-13 13:57:55 UTC 
* At least 2 hosts in pool.
* Host A is already SPM.
* Run spmStart on host B.
* Host B starts contending, even though another SPM already exists.
* Run spmStart on host B again.
* Output is "Operation not allowed while SPM is active" even though the host isn't actually SPM and is only contending.

[root@master-vds5 ~]# vdsClient -s 0 spmStart 81af6f63-6a25-4aaf-9ed9-7bf23fea7d13 1 1 1 1
58661c42-0747-4793-9eba-a5822f6e1dbe
[root@master-vds5 ~]# vdsClient -s 0 spmStart 81af6f63-6a25-4aaf-9ed9-7bf23fea7d13 1 1 1 1
Operation not allowed while SPM is active: ('81af6f63-6a25-4aaf-9ed9-7bf23fea7d13',)
Comment 1 Daniel Paikov 2011-12-13 13:58:36 UTC 
Created attachment 546226 [details]
vdsm.log
Comment 3 Ayal Baron 2011-12-13 14:04:50 UTC 
(In reply to comment #0)
> * At least 2 hosts in pool.
> * Host A is already SPM.
> * Run spmStart on host B.
> * Host B starts contending, even though another SPM already exists.

Up to here it is totally valid

> * Run spmStart on host B again.
> * Output is "Operation not allowed while SPM is active" even though the host
> isn't actually SPM and is only contending.

This is just a message issue

> 
> [root@master-vds5 ~]# vdsClient -s 0 spmStart
> 81af6f63-6a25-4aaf-9ed9-7bf23fea7d13 1 1 1 1
> 58661c42-0747-4793-9eba-a5822f6e1dbe
> [root@master-vds5 ~]# vdsClient -s 0 spmStart
> 81af6f63-6a25-4aaf-9ed9-7bf23fea7d13 1 1 1 1
> Operation not allowed while SPM is active:
> ('81af6f63-6a25-4aaf-9ed9-7bf23fea7d13',)
Comment 4 Itamar Heim 2013-03-11 21:58:25 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.