`floating ip pool list` does not work with Neutron (regression)

[Luigi Toscano]

This is a regression in the behavior of 3.0.1 from the previous versions. Compare:

$ openstack --version
openstack 1.7.2

Note: 2.2.0 behaves like 1.7.2 in this regard.

$ openstack ip floating pool list
+--------+
| Name |
+--------+
| public |
+--------+

(osc)$ openstack --version
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
openstack 3.0.1
(osc)$ openstack ip floating pool list
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
This command has been deprecated. Please use "floating ip pool list" instead.
Floating ip pool operations are only available for Compute v2 network.
(osc)$ openstack floating ip pool list
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
Floating ip pool operations are only available for Compute v2 network.

The deprecated command (ip floating pool list) does not work because the new version (floating ip pool list) does not support pool listing in Neutron. I understand that the concept of pool is different in Neutron, but the change can break existing users of OSC. It should follow the same deprecation rules of the commands.

Other commands work the same, even if deprecated.
1.7.2:
$ openstack ip floating list

$

3.0.1:
$ openstack ip floating list
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
This command has been deprecated. Please use "floating ip list" instead.

This is maybe related to https://bugs.launchpad.net/python-openstackclient/+bug/1566090 (i.e. maybe the code currently missing can fix both bugs).

[Richard Theis (rtheis)]

Hi Tang, can you please take a look at this bug?