Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Have commands changed? I receive errors like "'port' is not an openstack command."

Hi,

I've just updated the software on an Ubuntu 16.04 server that accesses my OpenStack configuration. This particular server only has python-openstackclient to interact with OpenStack. I was previously able to use the client without issues and I have written a number of scripts that use it to obtain information. Now, all of my scripts are broken:

$ openstack port list
openstack: 'port' is not an openstack command. See 'openstack --help'.
Did you mean one of these?
  port delete
  port show
  project create
  project delete
  project list
  project set
  project show

This has never been a problem before. One of my primary scripts used this command when allocating IP addresses. The most recent version of the documentation (for pike) says this is still a viable command: https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/port.html

Some commands also seem to have been reordered:

$ openstack floating ip list
openstack: 'floating' is not an openstack command. See 'openstack --help'.
Did you mean one of these?
  container create
  container delete
  container list
  container save
  container set
  container show
  container unset

no longer works, and

$ openstack ip floating list
+--------------------------------------+---------------------+------------------+--------------------------------------+
| ID                                   | Floating IP Address | Fixed IP Address | Port                                 |
+--------------------------------------+---------------------+------------------+--------------------------------------+
…

seems to have taken its place. The former command is still on the documentation (https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/floating-ip.html).

What has happened? Has this affected anyone else? Is this platform-specific?

I would appreciate any and all information so I can get things working again (on the most recent version)!

Thanks!

Have commands changed? I receive errors like "'port' is not an openstack command."

Hi,

I've just updated the software on an Ubuntu 16.04 server that accesses my OpenStack configuration. This particular server only has python-openstackclient to interact with OpenStack. I was previously able to use the client without issues and I have written a number of scripts that use it to obtain information. Now, all of my scripts are broken:

$ openstack port list
openstack: 'port' is not an openstack command. See 'openstack --help'.
Did you mean one of these?
  port delete
  port show
  project create
  project delete
  project list
  project set
  project show

This has never been a problem before. One of my primary scripts used this command when allocating IP addresses. The most recent version of the documentation (for pike) says this is still a viable command: https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/port.html

Some commands also seem to have been reordered:

$ openstack floating ip list
openstack: 'floating' is not an openstack command. See 'openstack --help'.
Did you mean one of these?
  container create
  container delete
  container list
  container save
  container set
  container show
  container unset

no longer works, and

$ openstack ip floating list
+--------------------------------------+---------------------+------------------+--------------------------------------+
| ID                                   | Floating IP Address | Fixed IP Address | Port                                 |
+--------------------------------------+---------------------+------------------+--------------------------------------+
…

seems to have taken its place. The former command is still on the documentation (https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/floating-ip.html).

I don't think I've broken anything. I can still use commands like openstack server create successfully on this server. The functions I am trying to use work from Horizon. My software is recent (All packages are up to date.) and I have since restarted the server.

What has happened? Has this affected anyone else? Is this platform-specific?

I would appreciate any and all information so I can get things working again (on the most recent version)!

Thanks!