Invalid API request during claim creation with maximum TTL

[Andrew Robbins]

To reproduce the issue:

$ openstack queue create Q1
+-------+-------+
| Field | Value |
+-------+-------+
| Name | Q1 |
+-------+-------+

# Then, post some messages to Q1 ...

$ openstack claim create --ttl 1209600 --grace 60 --limit 1 Q1
Error response from Zaqar. Code: 400. Title: Invalid API request. Description: The TTL for a claim may not exceed 1209600 seconds, and must be at least 60 seconds long..

You should see an error message similar to the above one. The weird thing is that this error does not happen for small TTLs, like 60.

[Andrew Robbins (agdrew)]

I found the exact value: --ttl 43200 works, but --ttl 43201 fails.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/310569
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=cae19a28864a753fd3c4aa8b1f88d3a4a8c12140
Submitter: Jenkins
Branch: master

commit cae19a28864a753fd3c4aa8b1f88d3a4a8c12140
Author: Fei Long Wang <email address hidden>
Date: Thu Apr 28 07:10:01 2016 +1200

    Fix wrong claim error message

    Now when create a claim with a big number, the message is not
    correct. It's showing the max TTL of message instead of claim.
    This patch fixes it.

    Closes-Bug: #1575870

    Change-Id: Ia948cc521a48101fa17ec23f49b5b03164f02940

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/zaqar 3.0.0.0b1 development milestone.