Bug 1565074
Summary: | targetcli: Storage Objects gets removed Upon restoreconfig, if the underlying backend is down | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Maurizio Lombardi <mlombard> | |
Component: | targetcli | Assignee: | Maurizio Lombardi <mlombard> | |
Status: | CLOSED ERRATA | QA Contact: | Martin Hoyer <mhoyer> | |
Severity: | high | Docs Contact: | ||
Priority: | urgent | |||
Version: | 7.4 | CC: | amukherj, bkunal, cww, dsundqvi, glamb, lmiksik, loberman, mchristi, mhoyer, mlombard, olim, prasanna.kalever, rcyriac, rhandlin, sabose, salmy | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: |
Previously, the targetcli utility removed storage objects under certain conditions. This happened when the volume hosting the storage objects was down and the user restored target configuration with the command "targetcli restoreconfig". With this update, configuration is now saved at a block granularity, and, as a result, the described problem no longer occurs.
|
Story Points: | --- | |
Clone Of: | 1524791 | |||
: | 1566108 (view as bug list) | Environment: | ||
Last Closed: | 2018-10-30 07:55:01 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1524791 | |||
Bug Blocks: | 1537170, 1546181, 1554642, 1559239, 1566108, 1592629 |
Comment 4
Prasanna Kumar Kalever
2018-04-09 15:27:09 UTC
Tested with kernel-3.10.0-915.el7: The issue is no longer reproducible; No regression found. (In reply to Martin Hoyer from comment #9) Forgot to mention tested targetcli package: - targetcli-2.1.fb46-6.el7 - python-configshell-1.1.fb23-4.el7 - python-rtslib-2.1.fb63-12.el7 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. https://access.redhat.com/errata/RHBA-2018:3040 |