** Changed in: keystonemiddleware
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1542486
Title:
nova-compute stack traces with
see comment #4
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1542486
Title:
nova-compute stack traces with
Jamie, we fixed it in puppet-nova:
https://review.openstack.org/#/c/276932/
** Changed in: puppet-nova
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
looks like middlware related, not keystone server, changing project
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
These changes all come from keystone libraries. Nova doesn't do any
registration of this config variables itself. Please poke the keystone
auth folks about this.
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
--
You
Adding Nova to the bug report because it absolutely should not require a
specific version of the Keystone API to make things work. I suspect
that there is a workaround here, but the Keystone API and auth plugins
are designed to be versionless. This is a step backwards, and should be
treated as a
6 matches
Mail list logo