IP groups improperly unimplemented [sic]

[Kevin L. Mitchell]

Attempts to create or delete an IP group result in a 501, since IP groups are unimplemented. However, attempts to retrieve or list IP groups result in an empty object, which seems to confuse novaclient enough to produce a runtime recursion exception (rackspace version of novaclient; bug reported on github). These remaining calls should probably also result in a 501, instead of this empty object.

[Brian Waldon (bcwaldon)]

As of rev 904, the resource is correctly unimplemented. Here are the status codes I saw in my testing with trunk rev 940:

GET http://172.19.0.3:8774/v1.0/shared_ip_groups -> 501
GET http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501
POST http://172.19.0.3:8774/v1.0/shared_ip_groups -> 501
PUT http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501
DELETE http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501

FYI, the resource is removed as of v1.1, so we see 404s across the board now:

GET http://172.19.0.3:8774/v1.1/shared_ip_groups -> 404
GET http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404
POST http://172.19.0.3:8774/v1.1/shared_ip_groups -> 404
PUT http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404
DELETE http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404

Kevin, if you believe this is correct, we can resolve this bug.

[Thierry Carrez (ttx)]

@Kevin: Marking FixCommitted per last comment, please reopen (set back to 'new') if this is not fixed to your liking.

[Kevin L. Mitchell (klmitch)]

On Tue, 2011-04-05 at 14:33 +0000, Brian Waldon wrote:
> As of rev 904, the resource is correctly unimplemented. Here are the
> status codes I saw in my testing with trunk rev 940:

The test suite I was developing indicates that the change did fix the
issue. Thanks!
--
Kevin L. Mitchell <email address hidden>