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.
Description of problem:
When having 2.2 NFS data-center with one rhel5 host in 2.2 cluster and one 3.0 cluster, rhel5 as spm performs some operations on master metadata and then rhel5 is sent to maintenance therefore rhel6 starts contending, empty list is returned while reading metadata.
Version-Release number of selected component (if applicable):
vdsm-86
How reproducible:
Sometimes (80%)
Steps to Reproduce:
1. Create 2.2 NFS data-center
2. Add 2.2 cluster with rhel5.x host within
3. Add 3.0 cluster with rhel6.x host within
4. With rhel5 as SPM Inactivate and re-activate master storage domain
5. Send rhel5 to Maintenance and wait till rhel6 starts condending
Actual results:
Metadata cannot be read by rhel6 (vdsm)
Expected results:
Metadata are readable by rhel6
Additional info:
We've tracked down this issue with Federico last week - I don't have relevant logs for it.
Comment 1Federico Simoncelli
2011-07-29 08:42:05 UTC
commit 327692258dc61498cc9e8e08eadbdae61245a37a
Author: Federico Simoncelli <fsimonce>
Date: Fri Jul 22 14:48:56 2011 +0000
BZ#726630 Use only os.access to check permissions
Change-Id: Ic7b892886416e866178ac88c04cbfb68ed0c055b
http://gerrit.usersys.redhat.com/733
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