yahoo-eng-team team mailing list archive

[Lance Bragstad <lbragstad@xxxxxxxxx>]

That appears to be an oslo.messaging configuration option [0]. Keystone
will "inherit" and expose them through the configuration library [1].
Working with the oslo community directly might help if you're having
configuration issues.

Is there a specific issue with keystone's usage of the oslo.messaging
library? If so, please feel free to post steps on how to recreate and
reopen the bug.

[0] https://github.com/openstack/oslo.messaging/blob/d925e112b5e4353fa07704c1468a38785ce817d7/oslo_messaging/transport.py#L63-L67
[1] https://github.com/openstack/keystone/blob/stable/ocata/etc/keystone.conf.sample#L243-L431

** Changed in: keystone
       Status: New => Incomplete

** Changed in: keystone
       Status: Incomplete => Invalid

-- 
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/1752265

Title:
  invalid "default_notification_exchange" config in keystone.conf  of O
  version

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  [environment]: openstack ocata version.

  [description]: I test event notifications in my devstack and find that 'default_notification_exchange' in [oslo_messaging_rabbit] section seemed invalid. The valid config is 'control_exchange' in [DEFAULT] section.
  I don't know if anyone else encount this problem? and I don't konw whether other version has this problem. If it is invalid, It should be removed.  

  the below link is keystone.conf
  https://github.com/openstack/keystone/blob/stable/ocata/etc/keystone.conf.sample

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1752265/+subscriptions