Bug 1386830
Summary: | When creating a storage domain fails due to ClusterLockInitError, it is ignored and action completes | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Simone Tiraboschi <stirabos> |
Component: | Core | Assignee: | Adam Litke <alitke> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Kevin Alon Goldblatt <kgoldbla> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.18.14 | CC: | alitke, amureini, bugs, stirabos, tnisan, ylavi |
Target Milestone: | ovirt-4.1.3 | Flags: | rule-engine:
ovirt-4.1+
|
Target Release: | 4.19.18 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-06 13:31:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simone Tiraboschi
2016-10-19 16:53:08 UTC
Moving out all non blocker\exceptions. Moving out all non blocker\exceptions. The underlying issue in the Gluster bug 1386443 was a storage configuration problem relating to alignment. However, we should fail to create the storage domain if we cannot initialize the lease. Otherwise, we will fail when trying to use that domain. INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra Adam, this bug is targetted to 4.1.3. You should either backport the patch to the 4.1 stable branch, or we should discuss retargetting it if you don't think this is zstream material. INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'v4.19.17' doesn't contain patch 'https://gerrit.ovirt.org/77566'] gitweb: https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=refs/tags/v4.19.17 For more info please contact: infra Backported. Clearing NEEDINFO. Hi Simone, Can you please provide steps to reproduce? Hi, We need steps to reproduce this bz in order to verify. Please advise Hi, We need steps to reproduce this bz in order to verify. Please advise This is difficult to reproduce without modifying vdsm code. You can either modify vdsm (1) OR try to create a setup (2) 1. To modify code: - Open /usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py - Edit the initSANLock function and insert a 'raise Exception()' statement inside the existing try/except block there. - Restart vdsm 2. To create a setup: - In a brand new DC with no domains login to the host on which you plan to use for creating an initial domain. - Run the following looping code in the terminal: leases=/rhev/data-center/*/*/dom_md/leases while true; do rm -f $leases; done - Attempt to create a domain. It should fail with ClusterLockInitError. Note that I used method 1 (editing code) to test this flow. Moving to Verified |