3par drivers terminate connection requires host validation

Bug #1214994 reported by Kurt Martin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Kurt Martin

Bug Description

The 3PAR backend does not allow FQDN host names (i.e. foo.rose.hp.com), it requires just foo without the rose.hp.com. The 3PAR driver are checking the host name in the initialize connection but not in the terminate connection. This is causing the following exception:

 HTTPNotFound: Not found (HTTP 404) 17 - host does not exist

Tags: 3par drivers
Changed in cinder:
assignee: nobody → Kurt Martin (kurt-f-martin)
Changed in cinder:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

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

Reviewed: https://review.openstack.org/43163
Committed: http://github.com/openstack/cinder/commit/5a49640ba85adceb9fe91f745e5e374c3ee5a112
Submitter: Jenkins
Branch: master

commit 5a49640ba85adceb9fe91f745e5e374c3ee5a112
Author: Kurt Martin <email address hidden>
Date: Wed Aug 21 09:38:54 2013 -0700

    3PAR driver terminate connection host validation

    The 3PAR backend does not allow FQDN host names (i.e. foo.rose.hp.com),
    instead it requires just foo without the rose.hp.com. This patch will
    now validate the host name in terminate connection by calling
    _safe_host just as it was doing in initialize connection when creating
    the host on the 3PAR backend.

    Change-Id: I52e90938c782473edc93f30672a0530ab5934edc
    Fixes: bug 1214994

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
milestone: none → havana-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: havana-3 → 2013.2
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.