← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 955792] Re: No public IP addresses listed in server representation

 

Please feel free to reopen if the issue reoccured

** Changed in: nova
       Status: In Progress => Confirmed

** Changed in: nova
       Status: Confirmed => 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/955792

Title:
  No public IP addresses listed in server representation

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  1. Create a VM 
  2. Wait till active 
  3. Attach a public ip to VM 
  4. SSH to VM using nova ssh 
  routray@ubuntu:~/Desktop/copy/st1$ nova ssh 
  usage: nova ssh [--private] [--login <login>] <server> 
  error: too few arguments 
  Try `nova help ssh' for more information. 

  
  routray@ubuntu:~/Desktop/copy/st1$ nova --debug ssh 106204 
  connect: (cs.systest.aw1.hpcloud.net, 35357) 
  send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: cs.systest.aw1.hpcloud.net:35357\r\nContent-Length: 150\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n{"auth": {"tenantName": "satya.routray@xxxxxx-default-tenant", "passwordCredentials": {"username": "satya.routray@xxxxxx", "password": "ca$hc0w!4#"}}}' 
  reply: 'HTTP/1.1 200 OK\r\n' 
  header: Content-Length: 3564 
  header: Content-Type: application/json 
  header: Date: Wed, 14 Mar 2012 10:29:28 GMT 
  header: Cache-Control: no-cache 
  header: Expires: -1 
  header: Pragma: no-cache 
  header: Server: Apache-Coyote/1.1 
  connect: (compute.systest.aw1.hpcloud.net, 443) 
  send: u'GET /v1.1/73438783064199/servers/106204 HTTP/1.1\r\nHost: compute.systest.aw1.hpcloud.net\r\nx-auth-project-id: satya.routray@xxxxxx-default-tenant\r\nx-auth-token: HPAuth_4f606bd1e4b0b829e4428dc9\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n' 
  reply: 'HTTP/1.1 200 OK\r\n' 
  header: Content-Length: 1015 
  header: Content-Type: application/json; charset=UTF-8 
  header: Date: Wed, 14 Mar 2012 10:29:32 GMT 
  ERROR: No public address found. 

  After little more debugging

  I found that the public ip assigned is listed under private

  <snip>
  RESP:{'date': 'Thu, 15 Mar 2012 07:17:00 GMT', 'status': '200', 'content-length': '1015', 'content-type': 'application/json; charset=UTF-8', 'content-location': u'https://compute.systest.aw1.hpcloud.net/v1.1/73438783064199/servers/106204&#39;} {"server": {"status": "ACTIVE", "updated": "2012-03-15T06:58:15Z", "hostId": "d303b97b5c36df3811814d8a707b22c219f622f88fb8ab397028e683", "user_id": "47101178638744", "name": "vm01", "links": [{"href": "https://compute.systest.aw1.hpcloud.net/v1.1/73438783064199/servers/106204";, "rel": "self"}, {"href": "https://compute.systest.aw1.hpcloud.net/73438783064199/servers/106204";, "rel": "bookmark"}], "addresses": {"private": [{"version": 4, "addr": "10.12.15.192"}, {"version": 4, "addr": "15.184.120.60"}]}, "tenant_id": "73438783064199", "image": {"id": "3172", "links": [{"href": "https://compute.systest.aw1.hpcloud.net/73438783064199/images/3172";, "rel": "bookmark"}]}, "created": "2012-03-14T10:15:12Z", "uuid": "c81949b6-dd1e-4993-ae4f-4c0e5b4225db", "accessIPv4": "", "accessIPv6": "", "key_name": "satya", "progress": 100, "flavor": {"id": "100", "links": [{"href": "https://compute.systest.aw1.hpcloud.net/73438783064199/flavors/100";, "rel": "bookmark"}]}, "config_drive": "", "id": 106204, "metadata": {}}} 
  <snip> 

  Might be this is the cause of this issue

  Guessing if we will have a public feild where the associated public ip
  will be located this issue may go away

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