yahoo-eng-team team mailing list archive

[Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>]

** Changed in: cloud-archive
       Status: New => Fix Released

** Changed in: keystone/ocata
       Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1677730

Title:
  keystone-manage mapping_engine is broken: TypeError

Status in Ubuntu Cloud Archive:
  Fix Released
Status in OpenStack Identity (keystone):
  Invalid
Status in OpenStack Identity (keystone) newton series:
  In Progress
Status in OpenStack Identity (keystone) ocata series:
  Fix Released
Status in keystone package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * 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.

  [Test Case]

   * Deploy keystone using Juju with this bundle:
     http://pastebin.ubuntu.com/24855409/

  
   * ssh to keystone unit, grab artifacts and run command:
     - mapping.json: http://pastebin.ubuntu.com/24855419/
     - input.txt: http://pastebin.ubuntu.com/24855420/
     - command:
     '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
  rules.

  [Regression Potential]

   * 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]
  Running `keystone-manage mapping_engine` (with parameters) is broken:

  2017-03-30 16:09:11.982 13513 CRITICAL keystone [-] TypeError: __init__() takes exactly 3 arguments (2 given)
  2017-03-30 16:09:11.982 13513 ERROR keystone Traceback (most recent call last):
  2017-03-30 16:09:11.982 13513 ERROR keystone   File "/usr/bin/keystone-manage", line 10, in <module>
  2017-03-30 16:09:11.982 13513 ERROR keystone     sys.exit(main())
  2017-03-30 16:09:11.982 13513 ERROR keystone   File "/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 44, in main
  2017-03-30 16:09:11.982 13513 ERROR keystone     cli.main(argv=sys.argv, config_files=config_files)
  2017-03-30 16:09:11.982 13513 ERROR keystone   File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1270, in main
  2017-03-30 16:09:11.982 13513 ERROR keystone     CONF.command.cmd_class.main()
  2017-03-30 16:09:11.982 13513 ERROR keystone   File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1143, in main
  2017-03-30 16:09:11.982 13513 ERROR keystone     rp = mapping_engine.RuleProcessor(rules['rules'])
  2017-03-30 16:09:11.982 13513 ERROR keystone TypeError: __init__() takes exactly 3 arguments (2 given)

  Affects mitaka, newton and ocata stable (centos-release).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1677730/+subscriptions