This bug was fixed in the package keystone - 2:10.0.2-0ubuntu1~cloud0
keystone (2:10.0.2-0ubuntu1~cloud0) xenial-newton; urgency=medium
[ Frode Nordahl ]
* d/p/keystone_manage_mapping_engine_fix.patch: Fix keystone-manage
mapping_engine usability issues (LP: #1655182).
[ James Page ]
* New upstream point release for OpenStack Newton (LP: #1705176).
** Changed in: cloud-archive/newton
Status: Fix Committed => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
keystone-manage mapping_engine tester problems
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive mitaka series:
Status in Ubuntu Cloud Archive newton series:
Status in OpenStack Identity (keystone):
Status in keystone package in Ubuntu:
Status in keystone source package in Xenial:
Status in keystone source package in Yakkety:
* A bug in keystone-manage tool prohibits the use of the
mapping_engine command for testing federation rules.
* Users of Keystone Federation will not be able to verify their
mapping rules before pushing these to production.
* Not being able to test rules before pushing to production is a
major operational challenge for our users.
* The proposed upload fixes this by backporting a fix for this issue
from upstream stable/ocata.
* Deploy keystone using Juju with this bundle:
* ssh to keystone unit, grab artifacts and run command:
- mapping.json: http://pastebin.ubuntu.com/24855419/
- input.txt: http://pastebin.ubuntu.com/24855420/
'keystone-manage mapping_engine --rules mapping.json --input input.txt'
* Observe that command provides no output and that a Python Traceback
is printed in /var/log/keystone/keystone.log
* Install the proposed package, repeat the above steps and observe
that the command now outputs its interpretation and effect of the
* keystone-manage mapping_engine is a operational test tool and is
solely used by the operator to test their rules.
* The distributed version of this command in Xenial and Yakkety does
currently not work at all.
* The change will make the command work as our users expect it to.
[Original bug description]
There are several problems with keystone-manage mapping_engine
* It aborts with a backtrace because of wrong number of arguments
passed to the RuleProcessor
* The --engine-debug option does not work.
* Error messages related to input data are cryptic and inprecise.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp