yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1481554@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1481554

Title:
  Return unintelligible message when create ipv6 subnet

Status in neutron:
  Expired

Bug description:
  version: master

  I just create a network , and then create a ipv6 subnet like "neutron subnet-create ${NETWORK_NAME}--ip-version 6 ::/126".
  But the server returned the message like:
  xxx@xxx:~$ neutron subnet-create ll ::/126 --ip-version 6
  Created a new subnet:
  +-------------------+--------------------------------------+
  | Field             | Value                                |
  +-------------------+--------------------------------------+
  | allocation_pools  | {"start": "::2", "end": "::3"}       |
  | cidr              | ::/126                               |
  | dns_nameservers   |                                      |
  | enable_dhcp       | True                                 |
  | gateway_ip        | ::1                                  |
  | host_routes       |                                      |
  | id                | 09470e62-8d09-445b-8a6c-6677da23fa17 |
  | ip_version        | 6                                    |
  | ipv6_address_mode |                                      |
  | ipv6_ra_mode      |                                      |
  | name              |                                      |
  | network_id        | 3985d44b-1054-4697-b372-20f06f6fdda7 |
  | subnetpool_id     |                                      |
  | tenant_id         | a089ad6018554142a57a9dd705f53c5b     |
  +-------------------+--------------------------------------+

  The gateway ip is the loopback address for ipv6. And the
  allocation_pools may make the user confused just like 0.0.0.2 /
  0.0.0.3 based on ipv4 addresses.

  This behavior is so strange, but I think this should be an error.So I
  need someone to confirm it.

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