Typo causes exceptions in get_record_set

There is a typo in the function get_record_set which causes exceptions in the 
script filling logs and causing process hiccups:

----------------------------------------
Exception happened during processing of request from ('10.228.0.1', 34053)
Traceback (most recent call last):
  File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.7/SocketServer.py", line 638, in __init__
    self.handle()
  File "./bin/route53d.py", line 265, in handle
    response = self.handle_update(msg)
  File "./bin/route53d.py", line 340, in handle_update
    APIRequest.add(rrset)
  File "./bin/route53d.py", line 95, in add
    current_rrset = self.get_record_set(rrset.name, rrset.rdtype)
  File "./bin/route53d.py", line 171, in get_record_set
    or result.next.record_type != qtype):
AttributeError: 'ResourceRecordSets' object has no attribute 'next'
----------------------------------------

See a fix attached.

Original issue reported on code.google.com by k...@ahlers.me on 21 Apr 2014 at 6:24

Attachments:

r53.patch

bpbp-boop / route53d

Typo causes exceptions in get_record_set #9