iSCSI iqn name RFC violation

Bug #1459243 reported by Lucas Alvares Gomes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Fix Released
Medium
Lucas Alvares Gomes

Bug Description

The name generated by Ironic for the iSCSI target is violating the RFC 3720 and RFC 3721. Currently the name we generate in Ironic is very simplistic: "iqn-<node UUID>" but this can mess up with some of tools that consumes it (internal folks reported it mess up with the targetcli from Dracut[1]).

[1] https://github.com/openstack/diskimage-builder/tree/master/elements/deploy-targetcli

For references:

https://tools.ietf.org/html/rfc3720#section-3.2.6.3.1

https://tools.ietf.org/html/rfc3721#page-5

Changed in ironic:
importance: Undecided → Medium
assignee: nobody → Lucas Alvares Gomes (lucasagomes)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ironic (master)

Fix proposed to branch: master
Review: https://review.openstack.org/186014

Changed in ironic:
status: New → In Progress
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ironic (master)

Reviewed: https://review.openstack.org/186014
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=accc67443e06c840e90f26318f57bc3f5a11fa8b
Submitter: Jenkins
Branch: master

commit accc67443e06c840e90f26318f57bc3f5a11fa8b
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed May 27 15:15:15 2015 +0100

    Fix: iSCSI iqn name RFC violation

    Pior to this patch the name generated by Ironic for the iSCSI target was
    violating the RFC 3720 and RFC 3721, and this was messing up with some
    tools consuming it (see deploy-targetcli element for diskimage-builder).

    This patch fixing this generating a name that complies to the RFCs.

    Change-Id: I27ae1321b4195483ad50c0a46e6912152a25af76
    Closes-Bug: #1459243

Changed in ironic:
status: In Progress → Fix Committed
Changed in ironic:
milestone: none → 4.0.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.