swift replication network should not be required

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

Bug Description

Since the galaxy role changes this bug has been re-introduced.

The replication network has to be specified which shouldn't be the case, and if the replication network is the same as the storage network it will cause failures.

Changed in openstack-ansible:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

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

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

Reviewed: https://review.openstack.org/160745
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=8cf39b11ff0dab230b6ad2698b7512679d05e2e1
Submitter: Jenkins
Branch: master

commit 8cf39b11ff0dab230b6ad2698b7512679d05e2e1
Author: Andy McCrae <email address hidden>
Date: Tue Mar 3 11:15:54 2015 +0000

    Ensure replication_network is not required for swift

    * Adjust config location variables for account, container, object
    variables, to name them more clearly.
    * Adjust config placement order, to happen after init scripts are
    created so that the service restart handler will work appropriately.
    * Ensure the init scripts for the replicator service are created
    appropriately whether a dedicated replication_network is or isn't used.
    * Ensure the dedicated replication network configuration is only created
    when replication_network is specified and different to storage_network.
    * Ensure the appropriate configuration section in the server.conf is
    only added when the replication_network is specified and different to
    the storage_network.

    Change-Id: I4b204a974bb0a217f5222b6aa0fa36aa8c23b999
    Closes-Bug: #1427599

Changed in openstack-ansible:
status: In Progress → Fix Committed
Changed in openstack-ansible:
status: Fix Committed → Fix Released
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.