Updating record (v1) returns 500 with PowerDNS backend

[Paul Glass]

Doing a PUT /v1/{domain_id}/records/{record_id} returns a 500 when using the PowerDNS backend.

Request:

PUT /v1/domains/e6e1deb3-e574-4a16-85f8-d1c604bb5c88/records/0efd7564-b5ff-4304-b096-ddd5ab46c251

{ "data": "202.202.202.203" }

Response:

{"code": 500, "type": "unknown", "request_id": "req-39e0576e-9f2b-4537-9730-ac844a48faed"}

And designate-api.log gives the error - Backend: Unknown backend failure: AttributeError("'Record' object has no attribute 'priority'",).

Adding in a null priority field to the request also gives errors.

Switching to `backend_driver = fake` in designate.conf causes this error to disappear.

I've narrowed the issue down to this commit: https://github.com/openstack/designate/commit/67cf6b7b6f76eeb4a9d76f27b827782e1527b480. That is, 67cf6b7 exhibits the issue while the previous commit (bd5aae2) does not.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/138717

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/138717
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=ac14927a22f6007a818112bcd01909c29e0afada
Submitter: Jenkins
Branch: master

commit ac14927a22f6007a818112bcd01909c29e0afada
Author: Endre Karlson <email address hidden>
Date: Wed Dec 3 14:15:06 2014 +0100

    Handle priority the same way as when create_record

    If not it assumes that priority is a part of the record which is now a part of
    the record.data

    Change-Id: I6c7921b88ac31b0c8f2ffa615e6b1237bcb0b4bc
    Closes-Bug: #1398587