OpenStack Heat

Rackspace Cloud DNS TTL constraints don't match API

Bug #1380755 reported by Jason Dunsmore
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Undecided
Jason Dunsmore
OpenStack Heat 2015.1.0 "kilo"
Jason Dunsmore (jasondunsmore)
Changed in heat:
assignee: nobody → Jason Dunsmore (jasondunsmore)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

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

Changed in heat:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/128061
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f5637d2eec6699cd8d36adf94291792490640d1b
Submitter: Jenkins
Branch: master

commit f5637d2eec6699cd8d36adf94291792490640d1b
Author: Jason Dunsmore <email address hidden>
Date: Mon Oct 13 14:24:12 2014 -0500

    Make Rackspace Cloud DNS TTL constraints match API

    The Rackspace Cloud DNS TTLs have a minimum constraint of 301, but,
    according to the API docs, the minimum is "300 seconds or more".

    Change-Id: I924889f859de4226d5e7517576e40d1fdbba3064
    Closes-Bug: #1380755

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
milestone: none → kilo-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.