Login "Unable to get cinder service list"

I would like to share with you the output of both CLI
$ cinder ( python-cinderclient )
and
$ openstack ( python-openstackclient )

Hi Miguel,

Thank you for reporting this and making Ubunt ubetter. What version of OpenStack are you hitting this on?

Thanks,
Corey

Does recreation of this bug require use of an older openstack-dashboard with newer endpoints?

Marking Incomplete for now until we can get more details for how to recreate.

What version of OpenStack are you hitting this on?
This is the information I got from the Cloud:
    Ubuntu 16.04 (Xenial)
    OpenStack Pike
        SDN: Neutron, OVS & VXLAN
        Block & Object Storage: Ceph
        Architecture:
    Juju 2.3.5
    MAAS 2.3.2

App Version Status Scale Charm Store Rev OS Notes
openstack-dashboard 12.0.2 active 3 openstack-dashboard jujucharms 258 ubuntu

Aswell, $ openstack endpoint list shows 2x different Volume service type: cinderv2 & cinderv3

Hi Miguel,

I deployed Pike with the OpenStack charms and wasn't able to recreate this. I may not be taking the right steps to recreate. If you can provide more details for how to recreate that would be useful.

I'm able to view all of the tabs at http://dashboard-ip/horizon/admin/info/ without seeing any warning messages. Please see attached image.

Thanks,
Corey

Note: For testing I used openstack-origin=cloud:xenial-pike.

Hello Corey,

This happens when the user logs in into Horizon and he received the message from image attached
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1776429/+attachment/5151656/+files/System_info%20Error.JPG

What information would you like me to gather?
user's cloud software version:

    Ubuntu 16.04 (Xenial)
    OpenStack Pike
    Juju 2.3.5
    MAAS 2.3.2

Miguel,

Let's not move this to "In Progress" until we actually can recreate it. "In Progress" means a fix is actively being worked on, and I have no idea what to fix. If you can provide details for how to recreate this then feel free to move the state to "New".

The bug report is currently incomplete. I've tried to recreate this with a pike deployment but am unable to. Can you please provide details for how to recreate? You mentioned in the original description that "This is because cinder (python-cinderclient) is deprecated when used with newer versions of the openstack endpoints." Can you explain what that means and how to get a deployment into that state? Is the deployment a mixed-release environment? For example, is cinder running a different release of OpenStack than horizon?

Thanks,
Corey

Another question is, did this start to occur after an upgrade to Pike?