Charms still render auth_uri which is deprecated for removal in Stein as of Queens

Bug #1786186 reported by Dmitrii Shcherbakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Glance Charm
Fix Released
High
Nikolay Vinogradov

Bug Description

Charms still render auth_uri which is deprecated for removal in Stein as of Queens:

https://github.com/openstack/keystonemiddleware/blob/stable/queens/keystonemiddleware/auth_token/_opts.py#L51-L67

    cfg.StrOpt('auth_uri',
               deprecated_for_removal=True,
               deprecated_reason='The auth_uri option is deprecated in favor'
               ' of www_authenticate_uri and will be removed in the S '
               ' release.',
               deprecated_since='Queens',
               help='Complete "public" Identity API endpoint. This endpoint'
               ' should not be an "admin" endpoint, as it should be accessible'
               ' by all end users. Unauthenticated clients are redirected to'
               ' this endpoint to authenticate. Although this endpoint should'
               ' ideally be unversioned, client support in the wild varies.'
               ' If you\'re using a versioned v2 endpoint here, then this'
               ' should *not* be the same endpoint the service user utilizes'
               ' for validating tokens, because normal end users may not be'
               ' able to reach that endpoint. This option is deprecated in'
               ' favor of www_authenticate_uri and will be removed in the S'
               ' release.'),

See charmhelpers/contrib/openstack/templates/section-keystone-authtoken

description: updated
summary: - Charms still render auth_url which is deprecated for removal in Stein as
+ Charms still render auth_uri which is deprecated for removal in Stein as
of Queens
Revision history for this message
Liam Young (gnuoy) wrote :

I think it makes sense to have one unified template fragment for keystone auth token which works for all openstack releases. To achieve this the template will need to know which release is being deployed hence: https://github.com/juju/charm-helpers/pull/224

Revision history for this message
James Page (james-page) wrote :

Marking this as High as Stein is in development so this work must be done for 19.04 charm release.

Changed in charm-glance:
milestone: none → 19.04
importance: Undecided → High
status: New → Triaged
David Ames (thedac)
Changed in charm-glance:
milestone: 19.04 → 19.07
Ryan Beisner (1chb1n)
Changed in charm-glance:
assignee: nobody → Nikolay Vinogradov (nikolay.vinogradov)
Revision history for this message
Nikolay Vinogradov (nikolay.vinogradov) wrote :
Revision history for this message
Nikolay Vinogradov (nikolay.vinogradov) wrote :
Changed in charm-glance:
status: Triaged → Fix Committed
David Ames (thedac)
Changed in charm-glance:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.