Bug 1162381
Summary: | update targetd in RHEL 7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Andy Grover <agrover> |
Component: | targetd | Assignee: | Tony Asleson <tasleson> |
Status: | CLOSED ERRATA | QA Contact: | Martin Hoyer <mhoyer> |
Severity: | unspecified | Docs Contact: | Milan Navratil <mnavrati> |
Priority: | unspecified | ||
Version: | 7.4 | CC: | bgoncalv, coughlan, fge, mhoyer, mnavrati, mthacker, tasleson |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: |
_targetd_ rebased to version 0.8.6
The _targetd_ packages have been upgraded to upstream version 0.8.6, which provides a number of bug fixes and enhancements over the previous version. Notably, the *targetd* service now runs on either Python 2 or Python 3 run time, and the following APIs have been added: *initiator_list*, *access_group_list*, *access_group_create*, *access_group_destroy*, *access_group_init_add*, *access_group_init_del*, *access_group_map_list*, *access_group_map_create*, and *access_group_map_destroy*.
Notable bug fixes include:
* *targetd* is now compliant with JSON-RPC response version 2.0.
* the *export_create* API can now be used to map the same LUN to multiple initiators.
* *targetd* now ensures that SSL certificates are present at start-up.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 20:43:39 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: | |||
Bug Blocks: | 1074659, 1385242 |
Description
Andy Grover
2014-11-11 01:04:34 UTC
moving this to 7.2 Tested with targetd-0.8.5-1.el7 No regression found. 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-2017:1982 |