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.
Created attachment 655977[details]
logs
Description of problem:
I activated one of my hosts and got wrong master domain or version.
looking at the info from getStorageDomainInfo I can see that in only one of my hosts we see the domain with master version 0 instead of 1.
after vdsm restart the issue was resolved
looks like it might be a cache issue
Version-Release number of selected component (if applicable):
vdsm-4.9.6-44.0.el6_3.x86_64
si24.5
How reproducible:
Steps to Reproduce:
1. in NFS, create a pool while 2 out of the 3 hosts are in maintenance
2. attach and activate iso and export domain
3. activate the two other hosts
Actual results:
one host is unable to connect to the pool with wrong master domain version
Expected results:
we should be able to connect to pool and not read from cache.
Additional info:
before and after vdsm restart:
[root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainsList
72ec1321-a114-451f-bee1-6790cbca1bc6
eebcad17-cbf7-4098-880d-81e2c2504169
74b2f39e-d374-4bda-b8a1-fb2aca984a5a
[root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4']
lver = -1
version = 3
role = Master
remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA
spm_id = -1
type = POSIXFS
class = Data
master_ver = 0
name = Dafna-01
[root@camel-vdsb vdsm]# service vdsmd restart
Shutting down vdsm daemon:
vdsm watchdog stop [ OK ]
vdsm stop [ OK ]
vdsm: libvirt already configured for vdsm [ OK ]
Starting iscsid:
Starting up vdsm daemon:
vdsm start [ OK ]
[root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4']
lver = 0
version = 3
role = Master
remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA
spm_id = 1
type = POSIXFS
class = Data
master_ver = 1
name = Dafna-01
my two other hosts:
[root@gold-vdsc ~]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4']
lver = 0
version = 3
role = Master
remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA
spm_id = 1
type = POSIXFS
class = Data
master_ver = 1
name = Dafna-01
[root@gold-vdsd ~]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a
pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4']
lver = 0
version = 3
role = Master
remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA
spm_id = 1
type = POSIXFS
class = Data
master_ver = 1
name = Dafna-01
Comment 2Federico Simoncelli
2012-12-12 10:14:16 UTC
(In reply to comment #1)
> Fede, is this a duplicate of bug 879253 ?
Yes I think we can close this as a duplicate of bug 879253. Dafna would you like to try to reproduce before closing?
Created attachment 655977 [details] logs Description of problem: I activated one of my hosts and got wrong master domain or version. looking at the info from getStorageDomainInfo I can see that in only one of my hosts we see the domain with master version 0 instead of 1. after vdsm restart the issue was resolved looks like it might be a cache issue Version-Release number of selected component (if applicable): vdsm-4.9.6-44.0.el6_3.x86_64 si24.5 How reproducible: Steps to Reproduce: 1. in NFS, create a pool while 2 out of the 3 hosts are in maintenance 2. attach and activate iso and export domain 3. activate the two other hosts Actual results: one host is unable to connect to the pool with wrong master domain version Expected results: we should be able to connect to pool and not read from cache. Additional info: before and after vdsm restart: [root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainsList 72ec1321-a114-451f-bee1-6790cbca1bc6 eebcad17-cbf7-4098-880d-81e2c2504169 74b2f39e-d374-4bda-b8a1-fb2aca984a5a [root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4'] lver = -1 version = 3 role = Master remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA spm_id = -1 type = POSIXFS class = Data master_ver = 0 name = Dafna-01 [root@camel-vdsb vdsm]# service vdsmd restart Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm stop [ OK ] vdsm: libvirt already configured for vdsm [ OK ] Starting iscsid: Starting up vdsm daemon: vdsm start [ OK ] [root@camel-vdsb vdsm]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4'] lver = 0 version = 3 role = Master remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA spm_id = 1 type = POSIXFS class = Data master_ver = 1 name = Dafna-01 my two other hosts: [root@gold-vdsc ~]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4'] lver = 0 version = 3 role = Master remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA spm_id = 1 type = POSIXFS class = Data master_ver = 1 name = Dafna-01 [root@gold-vdsd ~]# vdsClient -s 0 getStorageDomainInfo 74b2f39e-d374-4bda-b8a1-fb2aca984a5a uuid = 74b2f39e-d374-4bda-b8a1-fb2aca984a5a pool = ['85047de7-c841-4ff0-9ebb-3f722001b0b4'] lver = 0 version = 3 role = Master remotePath = filer01.qa.lab.tlv.redhat.com:/Dafna-GA spm_id = 1 type = POSIXFS class = Data master_ver = 1 name = Dafna-01