dashboard fails to connect to nova api

[David O'Dell]

release: newton
OS: xenial

In both my 3 node bare metal newton deployment and also when using the allinone role from the openstack-chef-repo horizon fails to display anything related to compute.

In horizon if you attempt to list the "compute services" on the system information page you get the following error in the UI.

"Error: Unable to get nova services list."

From the apache error log the error is:
"Call to list supported extensions failed. This is likely due to a problem communicating with the Nova endpoint. Host Aggregates panel will not be displayed."

However from the command line running `openstack hypervisor list` command successfully lists the active hypervisors.

In horizon other actions like listing other services and creating images etc... work fine.
Its only when it needs to access the nova endpoint is where it fails.

The nova endpoints for admin, public and private are :
http://127.0.0.1:8774/v2.1/%(tenant_id)s

To reproduce this just spin up the allinone role `chef exec rake allinone`, log into the dashboard and attempt to list the running hypervisors.

[Samuel Cassiba (scassiba)]

Thanks for the report!

A quick check of the cookbooks confirms tenant_id exists in multiple places: block-storage, common, compute, orchestraion and repo

[David O'Dell (dodizzle)]

Is it supposed to be something other and tenant_id?

If so I'll change it and verify today.

Thanks.

On 2/3/17 11:24 AM, Samuel Cassiba wrote:
> Thanks for the report!
>
> A quick check of the cookbooks confirms tenant_id exists in multiple
> places: block-storage, common, compute, orchestraion and repo
>

[Jeremy Nauck (jedihamster)]

Sounds like https://bugs.launchpad.net/horizon/+bug/1661456 which I came across just a couple days ago. In short, the chef recipes end up installing an incompatible version of python-openstackclient that will need to be removed or downgraded to 6.0.0.

[Jeremy Nauck (jedihamster)]

(edit, that package name that needs to be inspected is python-novaclient) Be aware that even after getting past this issue, I am still unable to launch instances, nor can I create volumes that are created based on the cirros image that is included.

[Dr. Jens Harbott (j-harbott)]

Jeremy: Does launching instances or creating volumes only fail via the dashboard or do you also see problems via the CLI? Did you restart apache2 after downgrading python-novaclient?

Also note that if your are testing on VMs, 8GB may be too little memory, better use at least 12GB in order to be on the safe side.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[Dr. Jens Harbott (j-harbott)]

I could reproduce both issues and the above two patches should fix them.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/431544
Committed: https://git.openstack.org/cgit/openstack/cookbook-openstack-block-storage/commit/?id=897f9a521875ac4c7b8e63b91c3a20141a4eae56
Submitter: Jenkins
Branch: master

commit 897f9a521875ac4c7b8e63b91c3a20141a4eae56
Author: Jens Rosenboom <email address hidden>
Date: Thu Feb 9 14:48:43 2017 +0100

    Fix creating volumes from Glance images

    We need to use Glance API v2 now.

    Change-Id: I24a4289f24348511f3e5f39b7bac970faf1c729b
    Partial-Bug: 1661708

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/431548
Committed: https://git.openstack.org/cgit/openstack/cookbook-openstack-common/commit/?id=3d06aeabbf58b20bd5b034f35cd00e686945db5a
Submitter: Jenkins
Branch: master

commit 3d06aeabbf58b20bd5b034f35cd00e686945db5a
Author: Jens Rosenboom <email address hidden>
Date: Wed Feb 8 14:37:04 2017 +0000

    Install openstackclient into virtualenv

    There may be issues caused by updated OpenStack python libraries being
    picked up by other services when we install python-openstackclient
    globally. So instead install it into its own virtualenv and create a
    symlink to the resulting binary.

    Change-Id: I43d9baf13dda20d39d3c52faf1f2322eee4884a3
    Partial-Bug: 1661708