keystone_service returns ignore_other_regions error in liberty

Bug #1560993 reported by Simon Pierre Desrosiers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Invalid
Undecided
Unassigned
OpenStack-Ansible
Invalid
Undecided
Unassigned

Bug Description

I am trying to port swiftacular from Havana to liberty.

The following line to create the service endpoint using keystone_service returns an error :
- name: create keystone identity point
  keystone_service: insecure=yes name=keystone type=identity description="Keystone Identity Service" publicurl="https://{{ keystone_server }}:5000/v2.0" internalurl="https://{{ keystone_server }}:5000/v2.0" adminurl="https://{{ keystone_server }}:35357/v2.0" region={{ keystone_region }} token={{ keystone_admin_token }} endpoint="https://127.0.0.1:35357/v2.0"

returns the following error

TASK [authentication : create keystone identity point] *************************
fatal: [swift-keystone-01]: FAILED! => {"changed": false, "failed": true, "msg": "value of ignore_other_regions must be one of: yes,on,1,true,1,True,no,off,0,false,0,False, got: False"}
 to retry, use: --limit @site.retry

The same task worked without a hitch with havana.

Revision history for this message
Steve Martinelli (stevemar) wrote :

looks like "keystone_service" is coming from ansible, and swiftacular uses ansible... not sure what the keystone server project itself can do about this, i'll open this bug against openstack-ansible too

Changed in keystone:
status: New → Invalid
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

This doesn't appear to relate to any code used in OpenStack-Ansible as a project. It does appear to be Ansible of some sort, and perhaps relates to the Ansible modules. If that is so then the bug should be raised against the Ansible project I guess.

Changed in openstack-ansible:
status: New → Invalid
Revision history for this message
Simon Pierre Desrosiers (simonpie) wrote :

I am sorry if I dont understand the change to the status, it seems to me this is a bug with the ansible keystone module. And this is the place I found (here https://github.com/openstack/keystone) where bug for the keystone module can be opened. Would you have the kindness of pointing to me where to open a bug if this is not the right place ?

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.