Bug 470438
| Summary: | iscsiadm -k 0 will start iscsid if not yet running | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hans de Goede <hdegoede> | ||||
| Component: | iscsi-initiator-utils | Assignee: | Mike Christie <mchristi> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 10 | CC: | agrover, hdegoede, mchristi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-11-26 06:22:26 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: | |||||||
| Attachments: |
|
||||||
Makes now sense to start iscsid when trying to stop it :) Looks ok. iscsi-initiator-utils-6.2.0.870-0.2.rc1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/iscsi-initiator-utils-6.2.0.870-0.2.rc1.fc10 This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping iscsi-initiator-utils-6.2.0.870-0.2.rc1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 322819 [details] PATCH: do not start iscsid when not running when iscsiadm -k 0 gets executed The autostart iscsid patch I did has one peculiarity, it will start iscsid when not running when "iscsiadm -k 0" gets executed, only to kill it immediately afterwards. The attached patch (against the original patch) fixes this. Mike if you ack this one I'll take care of the rest.