I believe you are authenticating with the keystone that is on the controller, rather than the one that is running in the container.

Refer to this section of the wiki

https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints

Once you are pointing at the nova that is running in the container, those nova commands should work as expected.

Al

From: Alonso, Juan Carlos [mailto:juan.carlos.alonso@intel.com]
Sent: Monday, February 11, 2019 10:30 AM
To: 'starlingx-discuss@lists.starlingx.io'
Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported?

Hi,

In order to launch instances from a volume snapshot, I use  nova boot command.

After deploy an STX containerized system this command is returning below error:

[wrsroot@controller-0 ~(keystone_admin)]$ nova boot –flavor <flavor_name> --snapshot <snapshot_name> --nic <net-id> <vm-name>

ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fdfd92b0650>: Failed to establish a new connection: [Errno 111] Connection refused',))

I tried with ‘source /etc/nova/openrc’ and ‘source /etc/platform/openrc’ authentication, both got the same issue.

Is this nova boot command still supported with containers?

Regards.

Juan Carlos Alonso