OpenStack Bundles

Bug #1830782
Comment #10

Comment 10 for bug 1830782

Revision history for this message

Alex Kavanagh (ajkavanagh) wrote on 2019-05-30: Re: openstack-dashboard gui not showing newly created project/users under newly domain

#10

Hi Rafael, ah, I think there is a bit of confusion here, (or I misunderstanding something here).

The charm version (296, 300) refers to when they were released:

keystone rev 296 - UploadTime: 2019-04-17T22:22:31.574Z
Keystone rev 300 - UploadTime: 2019-04-17T22:22:31.574Z

The actual keystone charm (and all the other OpenStack charms) are 'multi-series' which means they support Ubuntu Xenial (16.04) through to Ubuntu Disco (19.04) AND multiple versions of OpenStack: in fact the keystone charm is explicitly verified and supported on:
- trusty-mitaka
- xenial-mitaka
- xenial-ocata
- xenial-pike
- xenial-queens
- bionic-queens
- bionic-rocky
- bionic-stein

So, to be clear what you are running, please could you paste the output of "juju status keystone". It will look something like:

Model Controller Cloud/Region Version SLA Timestamp
neutron-gateway serverstack serverstack/serverstack 2.6.2 unsupported 19:45:25Z

App Version Status Scale Charm Store Rev OS Notes
keystone 14.0.1 active 1 keystone jujucharms 445 ubuntu

Unit Workload Agent Machine Public address Ports Message
keystone/0* active idle 1 10.5.0.11 5000/tcp Unit is ready

Machine State DNS Inst id Series AZ Message
1 started 10.5.0.11 7f39a66a-8c7e-4a63-a5fd-4a6f5a27eb27 bionic nova ACTIVE

I'm assuming you are changing the "openstack-origin" config value as well as issuing a 'juju upgrade-charm' command?

From the original juju status you did, I see that a few of the main apps are:

glance 18.0.0 active 1 glance jujucharms 281 ubuntu stain
keystone 14.0.1 active 1 keystone jujucharms 296 ubuntu rocky
openstack-dashboard 15.0.0

In this case, keystone 14.0.1 is a rocky release; however, the 300 rev keystone charm also support rocky, so there's no need to down-grade the charm, eve
openstack-dashboard 15.0.0 is Stein.

So, you're saying that keystone (rocky) works, but keystone (stein) doesn't? It would be useful if you could upgrade the keystone charm to the latest revision (300) BUT leave the keystone release as rocky and see if the error re-occurs or keeps working. This way we can tell if it is a charm issue (in general) or a packaging/charm issue to do with stein explicitly. Thanks.

Hi Rafael, ah, I think there is a bit of confusion here, (or I misunderstanding something here).

The charm version (296, 300) refers to when they were released:

keystone rev 296 - UploadTime: 2019-04-17T22:22:31.574Z
Keystone rev 300 - UploadTime: 2019-04-17T22:22:31.574Z

So, to be clear what you are running, please could you paste the output of "juju status keystone".  It will look something like:

Model            Controller   Cloud/Region             Version  SLA          Timestamp
neutron-gateway  serverstack  serverstack/serverstack  2.6.2    unsupported  19:45:25Z

App       Version  Status  Scale  Charm     Store       Rev  OS      Notes
keystone  14.0.1   active      1  keystone  jujucharms  445  ubuntu

Unit         Workload  Agent  Machine  Public address  Ports     Message
keystone/0*  active    idle   1        10.5.0.11       5000/tcp  Unit is ready

Machine  State    DNS        Inst id                               Series  AZ    Message
1        started  10.5.0.11  7f39a66a-8c7e-4a63-a5fd-4a6f5a27eb27  bionic  nova  ACTIVE

I'm assuming you are changing the "openstack-origin" config value as well as issuing a 'juju upgrade-charm' command?

From the original juju status you did, I see that a few of the main apps are:

glance 18.0.0 active 1 glance jujucharms 281 ubuntu stain
keystone 14.0.1 active 1 keystone jujucharms 296 ubuntu rocky
openstack-dashboard 15.0.0

In this case, keystone 14.0.1 is a rocky release; however, the 300 rev keystone charm also support rocky, so there's no need to down-grade the charm, eve
openstack-dashboard 15.0.0 is Stein.

So, you're saying that keystone (rocky) works, but keystone (stein) doesn't?  It would be useful if you could upgrade the keystone charm to the latest revision (300) BUT leave the keystone release as rocky and see if the error re-occurs or keeps working.  This way we can tell if it is a charm issue (in general) or a packaging/charm issue to do with stein explicitly.  Thanks.