← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1148536] Re: Attaching volume to instance failed on Hyper-V using IPv6

 

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-rc1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1148536

Title:
  Attaching volume to instance failed on Hyper-V using IPv6

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  I want to attach   iSCSI-based  volume to a instance on Hyper-V .  But
  the operation failed due to two issues .

  1) Test environment
       control node :  KVM  running all nova services except  nova-compute service  , cinder-scheduler ,cinder-api  services .
       compute node:  Hyper-V  (windows server 2012 ), running nova-compute service  ,cinder-volume service

  2) Test steps

      create a volume with 'cinder create 1'  ,  boot a instance on Hyper-V ,then run the following command  on control node
      'nova volume-attach 505d1eeb-4436-46dd-acb1-1ba50d2554e8 7b550385-a3e6-47f4-b7c8-acaee7d4316b /dev/sdh"

  3) Nova Issues

     1. Parse IPv6 address and port wrong  on  Hper-V compute driver
        https://github.com/openstack/nova/blob/master/nova/virt/hyperv/volumeutilsv2.py#48
        separator = target_portal.find(':')
        this line can't handle IPv6 address/port like '2002:96f:2458::96f:2458:3260'
        Need replace with separator = target_portal.rfind(':')

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1148536/+subscriptions