yahoo-eng-team team mailing list archive

[Tobias Urdin <tobias.urdin@xxxxxxxxx>]

** Changed in: puppet-neutron
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1585699

Title:
  Neutron Metadata Agent Configuration - nova_metadata_ip

Status in neutron:
  Fix Released
Status in puppet-neutron:
  Fix Released

Bug description:
  I am not sure if this constitutes the tag 'bug'. However it has lead
  us to some confusion and I feel it should be updated.

  This option in neutron metadata configuration (and install docs) is
  misleading.

  {{{
  # IP address used by Nova metadata server. (string value)
  #nova_metadata_ip = 127.0.0.1
  }}}

  It implies the need to present an IP address for the nova metadata
  api. Where as in actual fact this can be a hostname or IP address.

  When using TLS encrypted sessions, this 'has' to be a hostname, else
  this ends in a SSL issue, as the hostname is embedded in the
  certificates.

  I am seeing this issue with OpenStack Liberty, however it appears to
  be in the configuration reference for Mitaka too, so I guess this is
  accross the board.

  If this needs to be listed in a different forum, please let me know!

  Thanks

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