yahoo-eng-team team mailing list archive

[Joseph Lanoux <joseph.lanoux@xxxxxx>]

Public bug reported:

When doing a Nova API or curl call, Nova will always return the Keystone
publicURL. If peradventure a user was working in a setting using the
adminURL or the internalURL, the call would still return the publicURL.
This issue is not seen upstream because those URLs are all the same in
devstack.

Steps to reproduce:
- setup the Keystone publicURL as a FQDN
- do a Nova curl call with the Keystone internalURL or adminURL
- the Keystone publicURL FQDN is returned instead of the URL used in the call

The test_get_version_details Tempest test is failing for the same reason
in such an environment.

My understanding is that the publicURL is hardcoded somewhere in the
Nova configuration.

** Affects: nova
     Importance: Undecided
         Status: New

** Summary changed:

- Nova returns always the publicURL
+ Nova returns always the Keystone publicURL

** Description changed:

  When doing a Nova API or curl call, Nova will always return the Keystone
  publicURL. If peradventure a user was working in a setting using the
  adminURL or the internalURL, the call would still return the publicURL.
  This issue is not seen upstream because those URLs are all the same in
  devstack.
  
  Steps to reproduce:
  - setup the Keystone publicURL as a FQDN
  - do a Nova curl call with the Keystone internalURL or adminURL
- - the Keystone publicURL FDQN is returned instead of the URL used in the call
+ - the Keystone publicURL FQDN is returned instead of the URL used in the call
  
  The test_get_version_details Tempest test is failing for the same reason
  in such an environment.
  
  My understanding is that the publicURL is hardcoded somewhere in the
  Nova configuration.

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

Title:
  Nova returns always the Keystone publicURL

Status in OpenStack Compute (nova):
  New

Bug description:
  When doing a Nova API or curl call, Nova will always return the
  Keystone publicURL. If peradventure a user was working in a setting
  using the adminURL or the internalURL, the call would still return the
  publicURL. This issue is not seen upstream because those URLs are all
  the same in devstack.

  Steps to reproduce:
  - setup the Keystone publicURL as a FQDN
  - do a Nova curl call with the Keystone internalURL or adminURL
  - the Keystone publicURL FQDN is returned instead of the URL used in the call

  The test_get_version_details Tempest test is failing for the same
  reason in such an environment.

  My understanding is that the publicURL is hardcoded somewhere in the
  Nova configuration.

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