an unclear error info returned when create an ipv6 subnetpool associate to ipv4 address scope

Bug #1533034 reported by hgangwx
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Low
Unassigned

Bug Description

[Summary]
an unclear error info returned when create an ipv6 subnetpool associate to ipv4 address scope
[Topo]
devstack all-in-one node

[Description and expect result]
need to return a clear error info

[Reproduceable or not]
reproduceable

[Recreate Steps]
1) create an ipv4 address scope:
root@45-59:/opt/stack/devstack# neutron address-scope-create
--tenant-id ebbcdabd911340efa9a3430488c43304 scope1 --ip_version 4
Created a new address_scope:
+------------+--------------------------------------+
| Field | Value |
+------------+--------------------------------------+
| id | 8902c850-5e2a-41fd-898e-204d9cf0429e |
| ip_version | 4 |
| name | scope1 |
| shared | False |
| tenant_id | ebbcdabd911340efa9a3430488c43304 |
+------------+--------------------------------------+

2) create an ipv6 subnetpool associate to the ipv4 address scope,
an unclear error info returned:
root@45-59:/opt/stack/devstack# neutron subnetpool-create --pool-prefix
2::1/64 --address-scope scope1 pool1
Illegal subnetpool association: subnetpool <built-in function id> cannot
associate with address scope 8902c850-5e2a-41fd-898e-204d9cf0429e because
subnetpool ip_version is not 4.
root@45-59:/opt/stack/devstack#

ISSUE: "subnetpool <built-in function id>" is unclear, also not readable for user

[Configration]
reproduceable bug, no need

[logs]
reproduceable bug, no need

[Root cause anlyze or debug inf]
reproduceable bug

[Attachment]
None

linwei,wu (wlwwu)
Changed in python-neutronclient:
assignee: nobody → linwei,wu (wlwwu)
Revision history for this message
Akihiro Motoki (amotoki) wrote :

The error message is returned from neutron.

affects: python-neutronclient → neutron
tags: added: l3-ipam-dhcp
Changed in neutron:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: Confirmed → In Progress
Changed in neutron:
milestone: none → mitaka-rc1
importance: Low → High
Changed in neutron:
assignee: linwei,wu (wlwwu) → Cedric Brandily (cbrandily)
Changed in neutron:
milestone: mitaka-rc1 → newton-1
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Looks like things are not as broken as they appear.

Changed in neutron:
importance: High → Low
Changed in neutron:
milestone: newton-1 → newton-2
Changed in neutron:
milestone: newton-2 → newton-3
Changed in neutron:
milestone: newton-3 → newton-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/270649
Reason: this looks dead.

Changed in neutron:
status: In Progress → Incomplete
tags: added: low-hanging-fruit
Changed in neutron:
milestone: newton-rc1 → none
assignee: Cedric Brandily (cbrandily) → nobody
Revision history for this message
Ilya Popov (ilya-p) wrote :

Hello all !!!

Is it needed to fix something ? looks like user claim wasn't fixed finally

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in neutron:
status: Incomplete → Expired
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.