Record of all errors seen with Cloud Load Balancers

Using the following script:

"""
Script to see what responses CLB returns when it's immutable (BUILD,
PENDING_UPDATE, PENDING_DELETE, DELETED)
"""

from twisted.internet.task import deferLater, react

from twisted.internet.defer import gatherResults, inlineCallbacks

import json
import treq

@inlineCallbacks
def what_happens_when(clock, tenant_id, auth_token):
    """
    Hammer CLB while it's immutable and see what responses are.
    """
    lb_config = {
        "loadBalancer": {
            "name": "cyli-test",
            "protocol": "HTTP",
            "virtualIps": [
                {"type": "PUBLIC"}
            ]
        }
    }
    nodes = {
        "nodes": [
            {
                "address": "124.1.2.3",
                "port": 80,
                "condition": "ENABLED",
                "type": "PRIMARY"
            },
            {
                "address": "125.1.2.4",
                "port": 81,
                "condition": "ENABLED",
                "type": "SECONDARY"
            }
        ]
    }

    url = "/".join((
        "https://iad.loadbalancers.api.rackspacecloud.com/v1.0",
        tenant_id, "loadbalancers"))
    headers = {'x-auth-token': auth_token,
               'content-type': 'application/json',
               'accept': 'application/json'}

    @inlineCallbacks
    def see_how_responds(node_id='12345'):
        resps = yield gatherResults([
            treq.get('/'.join((url, lbid)), headers=headers),
            treq.post('/'.join((url, lbid, 'nodes')), headers=headers,
                      data=json.dumps(nodes)),
            treq.put('/'.join((url, lbid, 'nodes', node_id)),
                     headers=headers,
                     data=json.dumps({'condition': "DRAINING"})),
            treq.delete('/'.join((url, lbid, 'nodes')), headers=headers,
                        params={'id': node_id}),
            treq.delete('/'.join((url, lbid)), headers=headers),
            treq.get('/'.join((url, lbid, "nodes")), headers=headers)
        ])

        bodies = yield gatherResults(
            [treq.json_content(resp) for resp in resps])

        print "------"
        print bodies[0]['loadBalancer']['status']
        for i, thing in enumerate(["ADD N:    ", "CHANGE N: ",
                                   "DEL N:    ", "DEL LB:   ",
                                   "LIST N:   "]):
            print thing, resps[i + 1].code
            print json.dumps(bodies[i + 1])
            print "------"

    resp = yield treq.post(url, headers=headers, data=json.dumps(lb_config))
    assert resp.code == 202
    lbid = str((yield treq.json_content(resp))['loadBalancer']['id'])
    yield see_how_responds()

    # should be in active state after 60 seconds - add a node
    resp = yield deferLater(
        clock, 60, treq.post,
        '/'.join((url, lbid, 'nodes')), headers=headers,
        data=json.dumps({"nodes": [{"address": "123.1.2.1",
                                    "port": 8080,
                                    "condition": "ENABLED",
                                    "type": "PRIMARY"}]}))
    assert resp.code == 202
    node_id = str((yield treq.json_content(resp))['nodes'][0]['id'])
    yield see_how_responds(node_id)

    # shoudl be in active state again after 60 seconds - deleted CLB
    resp = yield deferLater(clock, 60, treq.delete, '/'.join((url, lbid)),
                            headers=headers)
    yield see_how_responds(node_id)

    # should be in deleted state now
    resp = yield deferLater(clock, 60, lambda: None)
    yield see_how_responds(node_id)

if __name__ == "__main__":
    tenant_id = raw_input("Tenant ID: ")
    auth_token = raw_input("Auth token for " + tenant_id + ": ")
    react(what_happens_when, [tenant_id, auth_token])

I got the following results:

If the CLB is in BUILD:
- Adding a node results in {"message": "Load Balancer '116301' has a status of 'BUILD' and is considered immutable.", "code": 422}
- Changing a non-existent node results in {"message": "Node not found", "code": 404}
- Deleting a non-existent node results in {"message": "LoadBalancer is not ACTIVE", "code": 422}
- Deleting the CLB results in {"message": "Must provide valid load balancers: 116301 are immutable and could not be processed.", "code": 400}
- Listing nodes results in a 200 with an empty list of nodes
If the CLB is in PENDING_UPDATE:
- Adding a node results in {"message": "Load Balancer '116303' has a status of 'PENDING_UPDATE' and is considered immutable.", "code": 422}
- Changing an existing node results in {"message": "Load Balancer '116303' has a status of 'PENDING_UPDATE' and is considered immutable.", "code": 422}
- Deleting an existing node results in {"message": "LoadBalancer is not ACTIVE", "code": 422}
- Deleting the CLB results in {"message": "Must provide valid load balancers: 116303 are immutable and could not be processed.", "code": 400}
- Listing nodes results in a 200 with all the nodes currently on the CLB
If the CLB is in PENDING_DELETE:
- Adding a node results in {"message": "Load Balancer '116303' has a status of 'PENDING_DELETE' and is considered immutable.", "code": 422}
- Changing an existing node results in {"message": "Load Balancer '116303' has a status of 'PENDING_DELETE' and is considered immutable.", "code": 422}
- Deleting an existing node results in {"message": "LoadBalancer is not ACTIVE", "code": 422}
- Deleting the CLB results in {"message": "Must provide valid load balancers: 116303 are immutable and could not be processed.", "code": 400}
- Listing nodes results in a 200 with all the nodes on the CLB prior to deletion
If the CLB is in DELETED:
- Adding a node results in {"message": "The load balancer is deleted and considered immutable.", "code": 422}
- Changing an existing node results in {"message": "The loadbalancer is marked as deleted.", "code": 410}
- Deleting an existing node results in {"message": "The load balancer is deleted and considered immutable.", "code": 422}
- Deleting the CLB results in {"message": "Must provide valid load balancers: 116303 could not be found.", "code": 400}
- Listing nodes results in {"message": "The loadbalancer is marked as deleted.", "code": 410}

No idea what the error messages are if CLB is in ERROR, since that is not something trigger-able on demand.

rackerlabs / mimic

Record of all errors seen with Cloud Load Balancers #270