swift_proxy_vars shouldn't be required.

Bug #1469134 reported by Andy McCrae
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Andy McCrae
Kilo
Fix Released
High
Andy McCrae
Trunk
Fix Released
High
Andy McCrae

Bug Description

The patch to add read/write affinity has made swift_proxy_vars to be a required var.

This should be fixed.

Changed in openstack-ansible:
status: Confirmed → In Progress
Dolph Mathews (dolph)
Changed in openstack-ansible:
milestone: none → 11.0.4
Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
Kevin Carter (kevin-carter) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/196705
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=7697b559ff0e5d3033a6a1cf70d34bd5e412299c
Submitter: Jenkins
Branch: kilo

commit 7697b559ff0e5d3033a6a1cf70d34bd5e412299c
Author: Andy McCrae <email address hidden>
Date: Fri Jun 26 12:52:48 2015 +0100

    Make swift_proxy_vars not a required variable

    The swift_proxy_vars settings per swift-proxy_hosts entry should not be
    a required variable. This patch ensures that if it isn't specified the
    plays will still run as normal.

    Change-Id: I0ce8c3781c6fccb0fd757498222d1dab6124313f
    Closes-Bug: #1469134
    (cherry picked from commit 79f3267769cc3b8d0859e89d703b00ad613ae2e9)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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