yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => kilo-1

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

Title:
  EC2 metadata retuns ip of instance and ip of nova-api service node

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  curl -vL http://169.254.169.254/latest/meta-data/local-ipv4/
  * About to connect() to 169.254.169.254 port 80 (#0)
  *   Trying 169.254.169.254... connected
  * Connected to 169.254.169.254 (169.254.169.254) port 80 (#0)
  > GET /latest/meta-data/local-ipv4/ HTTP/1.1
  > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
  > Host: 169.254.169.254
  > Accept: */*
  > 
  < HTTP/1.1 200 OK
  < Content-Type: text/html; charset=UTF-8
  < Content-Length: 12
  < Date: Sun, 22 Jun 2014 15:15:52 GMT
  < 
  * Connection #0 to host 169.254.169.254 left intact
  * Closing connection #0
  192.168.0.22, 10.2.0.50

  192.168.0.22 - instance ip 10.2.0.50 - controller ip

  Happens only for /latest/meta-data/local-ipv4/

  Quick investigation shows that the issue is caused by

  https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L243
  (https://github.com/openstack/nova/blo...)

  'local-ipv4': self.address or fixed_ip, string

  self.address variable contains "192.168.0.22, 10.2.0.50" while
  fixed_ip contains correct "192.168.0.22" value.

  The workaround is: swapping those two variables: 'local-ipv4':
  fixed_ip or self.address, and restart of all nova-compute services

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