[keystone_v3 mainline]keystone V3 not provisioned properly still seeing v2 configuration in conf files

Bug #1702423 reported by aswani kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
Fix Released
Low
aswani kumar
Trunk
Fix Released
Critical
aswani kumar

Bug Description

keystone v3 mainline build 3077 mitaka
keystone v3 R4.0.1 build 22 mitaka

V3 configuration was missing in all below configuration files.

/etc/nova/nova.conf
/etc/neutron/neutron.conf
/etc/heat/heat.conf
/etc/glance/glance-api.conf
/etc/glance/glance-registry.conf

auth_version was not updated to 'v3' seeing <None> every where
[keystone_authtoken]
#auth_version = <None>

In external and internal ansible conf

/etc/contrail/config.global.js
config.identityManager.apiVersion = ['v2.0'];

tags: added: blocker
summary: - [keystone_v3 mainline]keystone V3 not provisioned properly still seeind
- v2 configuration
+ [keystone_v3 mainline]keystone V3 not provisioned properly still seeing
+ v2 configuration in conf files
Jeba Paulaiyan (jebap)
tags: added: server-manager
Revision history for this message
Dheeraj Gautam (dgautam) wrote :

Needs some more information about the issue
* what is the configuration tried for enabling keystone v3 ? By default, keystone v3 is not enabled. This needs to be configured specifically.

Revision history for this message
aswani kumar (aswanikumar90) wrote :

tested this in build 23 4.0 not seeing the issue.
not removing the milestone for 4.0 just to watch out for next couple of builds
lowering the priority for 4.0.1 milestone

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.