Bug 1586226
| Summary: | [targetcli] saveconfig: way to block-level save with delete command [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | targetcli | Assignee: | Maurizio Lombardi <mlombard> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Hoyer <mhoyer> |
| Severity: | urgent | Docs Contact: | Marek Suchánek <msuchane> |
| Priority: | high | ||
| Version: | 7.5 | CC: | cww, lmanasko, mchristi, mhoyer, mlombard, prasanna.kalever, rcyriac, rhandlin, salmy, tdosek |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | targetcli-2.1.fb46-6.el7_5 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously, it was not possible to use the block-level "saveconfig" command after deleting objects with the "delete" command. As a consequence, restarting the targetcli service reloaded the deleted objects. This update introduces the "save" flag of the "delete" command. Setting this flag to "True" automatically saves the configuration. As a result, it is now possible to save configuration on the block level when deleting an object.
|
Story Points: | --- |
| Clone Of: | 1585152 | Environment: | |
| Last Closed: | 2018-06-26 16:56:46 UTC | Type: | --- |
| 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: | 1585152 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-06-05 18:51:14 UTC
Tested with: python-rtslib-2.1.fb63-12.el7_5 targetcli-2.1.fb46-6.el7_5 No regression found. The block-level delete command with safe=True works as expected. 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:1999 |