CONF.placement.os_interface is not used in nova-status upgrade check
Bug #1664334 reported by
Matt Riedemann
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann | ||
Ocata |
Fix Committed
|
Undecided
|
Matt Riedemann |
Bug Description
https:/
However, that change was (1) missing unit tests and (2) didn't include using that option in the nova-status upgrade check code here:
tags: | added: ocata-rc-potential |
To post a comment you must log in.
The other issue is the choices in the config option are too restrictive. keystoneauth1 doesn't actually validate the interface values, and 'auth' is a valid value meaning, don't lookup the endpoint in the service catalog, use the configured auth_url instead.
Keystone v3 API validates the endpoint interfaces to be one of admin/public/ internal:
https:/ /github. com/openstack/ keystone/ commit/ 8ef267c3ee3f0f1 e6bdb74da7ed68a eb958e5567
But keystone v2 doesn't, and the keystone v3 schema validation could theoretically change over time so we shouldn't encode that list in nova too when it's already in keystone when you create the endpoint.