Red Hat Bugzilla – Bug 867947
vdsClient should not show storage domains not in the storage pool
Last modified: 2016-02-10 12:59:10 EST
Created attachment 629542 [details]
Description of problem:
running vdsClient -s 0 getStorageDomainsList in both my hosts I see 9 domains in spm and 8 in hsm.
the domain not showing is a domain which is unattached to the pool (see screen shot attached on 9 domains and attached files showing only 8 in hsm)
after speaking to Edu he thinks its a backend bug so opening on backend.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add domains to DC with only one host + create domains but do not attach them
2. after domains are active add a second host to DC (do not install, just move from different DC).
we see different results of domains in vgs
both hosts should have same results
Additional info: logs, vgs, device list, domains list from both hosts are attached
The LUNs view from hosts gold-vdsc(spm) and gold-vdsd(hsm) is different.
Is required for the proper function of the system to the two views to be identical.
Please check the storage configuration.
LUN 3600140531258b628dbb4710b04713bb7 can't be seen in gold-vdsd.
This LUN contains VG 47c27c7e-6238-4d0e-8d62-d97c5c2e93ee which is the SD named "testi-01"
This is the lacking SD.
In spite that the connections are identical two luns are not exposed by the LIO_ORG,IBLOCK target to the gold-vdsd host.
3600140531258b628dbb4710b04713bb7 dm-72 LIO-ORG,IBLOCK
360014052ebfb4b09b1b488f80ccae54c dm-106 LIO-ORG,IBLOCK
36001405fadabd60ec0e4369b3e61eba5 dm-105 LIO-ORG,IBLOCK
360014058faf7546269744f582b3366fa dm-104 LIO-ORG,IBLOCK
36001405fadabd60ec0e4369b3e61eba5 dm-108 LIO-ORG,IBLOCK
360014058faf7546269744f582b3366fa dm-109 LIO-ORG,IBLOCK
Active connections in the two hosts:
SDs in gold-vdsc:
'dbed4cf3-a177-49a8-b41c-f12b85db4286', '47c27c7e-6238-4d0e8d62-d97c5c2e93ee', 'd95cd4e5-166a-4901-84f5-64eaca97d4c6', 'ede8ec4d-ba09-48df-ad0a-7c1e978d4a7c', '402471a6-154f-43a3-b9fe-5308024c33a6', '169e9862-88c7-4ba2-84ce-b7efdb298ab0', '76f6a2e6-e2a3-431c-a8ef-f5d58aa00629', 'ac6943fb-d267-45c3-a5af-128a6e761a2e', '597dd01f-c2fc-47b1-b19a-c3eec053d336', 'fb891cd0-355f-4584-a8c4-de7fdab3e47b'
SDs in gold-vdsd:
'dbed4cf3-a177-49a8-b41c-f12b85db4286', '402471a6-154f-43a3-b9fe-5308024c33a6', 'd95cd4e5-166a-4901-84f5-64eaca97d4c6', 'ede8ec4d-ba09-48df-ad0a-7c1e978d4a7c', '169e9862-88c7-4ba2-84ce-b7efdb298ab0', '76f6a2e6-e2a3-431c-a8ef-f5d58aa00629', 'ac6943fb-d267-45c3-a5af-128a6e761a2e', '597dd01f-c2fc-47b1-b19a-c3eec053d336'
I managed to reproduce.
1. hsm only shows domains in pool when we run vgs. if we detach a domain hsm will no longer show it.
2. put hsm host in maintenance -> put domains in maintenance -> detach domains
the hsm will still show the connection of the luns when running iscsiadm -m session but vgs will show only domains in pool
Created attachment 630915 [details]
I could not make heads or tails of this bug.
What exactly is the problem?
When you create a domain but do not attach it to another host, why would you expect to see it on other hosts?
(In reply to comment #4)
> I could not make heads or tails of this bug.
> What exactly is the problem?
> When you create a domain but do not attach it to another host, why would you
> expect to see it on other hosts?
Ayal, the problem is as follows:
- we have a pool with several domains and 2 hosts
- we detach one of the domains:
- from some-reason, engine send connectStorageServer to this domain (in detached state) to one of the hosts, hence, domain (VG) is visible on that host.
expected result: engine should not try to connect this server, up until user asks for it and tries to attach it to pool again.
in any case, this implies on an inconsistent behavior where engine send the connect to one of the hosts and not the other.
I have two hosts in one cluster with 8 domains attached to pool and two unattached.
when I ran vdsClient from both hosts I could see 8 domains in one host and 9 domains in the other.
vdsClient reported 1 or the unattached domains in one host although it was not part of the pool (it is in the setup but not in the pool).
this is all the bug is about - do not show domains which are not connected to the pool in vdsClient
> this is all the bug is about - do not show domains which are not connected
> to the pool in vdsClient
Changing component and rephrasing title based on this comment
Does is happens in 3.3?
(In reply to Nir Soffer from comment #8)
> Does is happens in 3.3?
Please direct questions to Aharon since I am no longer working on rhevm.
using 3.3 is27,
both SPM and HSM show all SDs (attached and Unattached) the same
I am not sure if we want to see the unattached domains when running vgs or vdsClient.
1. created ISCSI DC with 2 hosts
2. added 5 SDs (few attached few unattached)
3. run vgs and vdsClient
(In reply to Aharon Canan from comment #10)
> using 3.3 is27,
> both SPM and HSM show all SDs (attached and Unattached) the same
> I am not sure if we want to see the unattached domains when running vgs or
vgs will show everything lvm sees, we cannot and do not want to change that.
But limiting domains in vdsClient sounds reasonable.
I don't think this is a bug (nor that we should do anything at all).
WRT to getStorageDomainsList returns (by design) all the visible storage domains. If you specify an (optional) storage pool, then it displays only the relevant storage domains (part of the pool).
# vdsClient 0 getStorageDomainsList
# vdsClient 0 getStorageDomainsList 98da1408-948d-4cab-9a8b-418914be9f07
As far as I know the engine is aware of this behavior.