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.
Bug 884318 - 3.1.z - [vdsm] ConnectStoragePool fail with 2 hosts in NFS due to stale cache
Summary: 3.1.z - [vdsm] ConnectStoragePool fail with 2 hosts in NFS due to stale cache
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: All
urgent
urgent
Target Milestone: rc
: 6.3
Assignee: Federico Simoncelli
QA Contact: Gadi Ickowicz
URL:
Whiteboard: storage
Depends On: 879253
Blocks: 896518
TreeView+ depends on / blocked
 
Reported: 2012-12-05 22:13 UTC by Chris Pelland
Modified: 2014-08-22 01:41 UTC (History)
16 users (show)

Fixed In Version: vdsm-4.9.6-44.2
Doc Type: Bug Fix
Doc Text:
When connecting to a storage pool VDSM did not always refresh the storage domain cache. As a result of the stale cache VDSM did not detect changes made to the storage by other hosts. VDSM has been updated and the connectStoragePool command now refreshes the storage domain cache before connecting to the storage pool.
Clone Of:
: 896518 (view as bug list)
Environment:
Last Closed: 2013-01-15 14:52:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdsm + engine logs (1.66 MB, application/x-gzip)
2012-12-11 16:15 UTC, Gadi Ickowicz
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0159 0 normal SHIPPED_LIVE vdsm bug fix update 2013-01-15 19:50:47 UTC

Description Chris Pelland 2012-12-05 22:13:54 UTC
This bug has been copied from bug #879253 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 6 Federico Simoncelli 2012-12-06 10:50:20 UTC
commit 9d042bdd276c4a3a6c75fe506bb5897044c8ebf8
Author: Federico Simoncelli <fsimonce>
Date:   Thu Nov 22 09:04:00 2012 -0500

    sdcache: add refresh to connectStoragePool
    
    Change-Id: I2d3adcff7bb0e97be5c797cd720c6353920d9db0
    Signed-off-by: Federico Simoncelli <fsimonce>

http://gerrit.ovirt.org/#/c/9422/

Comment 8 Stephen Gordon 2012-12-10 18:53:59 UTC
Federico, please review the "Doc Text" to ensure it correctly reflects the change.

Comment 9 Federico Simoncelli 2012-12-11 11:20:54 UTC
(In reply to comment #8)
> Federico, please review the "Doc Text" to ensure it correctly reflects the
> change.

The "Doc Text" is accurate.

Comment 10 Gadi Ickowicz 2012-12-11 16:15:33 UTC
Created attachment 661535 [details]
vdsm + engine logs

verified on vdsm vdsm-4.9.6-44.2.el6_3.x86_64 - connectStoragePool succeeds on both hosts.

Comment 12 errata-xmlrpc 2013-01-15 14:52:53 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/RHBA-2013-0159.html


Note You need to log in before you can comment on or make changes to this bug.