[Yahoo-eng-team] [Bug 1188944] Re: Single fixed_ip allocated to an instance can be deleted and not assigned again on request

2013-09-08 Thread Christopher Yeoh 
The return code is 202 and is returned before its known if the operation
has succeeded or not.

Defintion for 202 is  The request has been accepted for processing, but
the processing has not been completed. The request may or may not
eventually be acted upon, as it may be disallowed when processing
actually takes place. there is no facility for status returns from
asynchronous operations such as this. 


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

Title:
  Single fixed_ip allocated to an instance can be deleted and not
  assigned again on request

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Hi
  I am using devstack (current master branch, may be of havana release) and 
launched an instance from cirros image as following:-

  
+--+--+++-++
  | ID   | Name | Status | Task State | 
Power State | Networks   |
  
+--+--+++-++
  | eb251761-50f0-4a00-9062-a572ff7af834 | CIRROS-1 | ACTIVE | None   | 
Running |   private=10.0.0.2  |

  Now I deleted the fixed ip using below CLI:-

  $$ nova remove-fixed-ip CIRROS-1 10.0.0.2

  And it removed fixed ip successfully:-
  
+--+--+++-++
  | ID   | Name | Status | Task State | 
Power State | Networks   |
  
+--+--+++-++
  | eb251761-50f0-4a00-9062-a572ff7af834 | CIRROS-1 | ACTIVE | None   | 
Running ||

  Now I again want to add fixed_ip and tried many times using below CLIs:-
  $$nova  add-fixed-ip CIRROS-1 10.0.0.4
  $$nova  add-fixed-ip CIRROS-1 10.0.0.2

  But above CLIs neither give error nor allocate fixed_ip to instance.

  I tried it with both user i.e. demo and admin, and also try to ping
  that IPs but not working.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1182883] Re: List servers matching a regex fails with Quantum

2013-09-08 Thread Christopher Yeoh 
** Changed in: nova
   Status: New = Invalid

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

Title:
  List servers matching a regex fails with Quantum

Status in OpenStack Neutron (virtual network service):
  Invalid
Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  Confirmed

Bug description:
  The test
  
tempest.api.compute.servers.test_list_server_filters:ListServerFiltersTestXML.test_list_servers_filtered_by_ip_regex
  tries to search a server with only a fragment of its IP (GET
  http://XX/v2/$Tenant/servers?ip=10.0.) which calls the following
  Quantum request :
  http://XX/v2.0/ports.json?fixed_ips=ip_address%3D10.0. But it seems
  this regex search is not supporter by Quantum. Thus the tempest test
  fauls.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1196255] Re: Cannot filter 'soft-deletd' instances via nova api

2013-09-08 Thread Christopher Yeoh 
** Changed in: nova
   Status: New = Won't Fix

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

Title:
  Cannot filter 'soft-deletd' instances via nova api

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  In nova-api, both DELETED and SOFT_DELETED are mapped to 'DELETED'.
  Thus we cannot filer 'soft-deleted' instances via nova-api, like:

  nova list --status SOFT_DELETED

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1205841] Re: API deallocate Floating IP address

2013-09-08 Thread Christopher Yeoh 
Looks like this has been fixed in the doco

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

Title:
  API deallocate Floating IP address

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Try to deallocate a floating IP from a tenantID throgh http API, the
  address should be v2/{tenant_id}/os-floating-ips/{ip_id}, rather than
  v2/{tenant_id}/os-floating-ips which is found at:
  http://api.openstack.org/api-ref.html#ext-floating-ips

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp