Replicas are scheduled on the same host as the primary

Bug #1554282 reported by Goutham Pacha Ravi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
High
Goutham Pacha Ravi

Bug Description

Currently, while scheduling a new replica, the ShareReplicationFilter passes any host that shares the
replication_domain of the active replica's host. On successive runs on the CI, it was observed that the same
host was chosen multiple times. In a real deployment, there is no practicality in allowing replication
within the same pool.

Changed in manila:
assignee: nobody → Goutham Pacha Ravi (gouthamr)
Changed in manila:
status: New → In Progress
Changed in manila:
milestone: none → mitaka-rc1
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/291287
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=0616fcb8fe4ef2734db4b0107a220068170e8683
Submitter: Jenkins
Branch: master

commit 0616fcb8fe4ef2734db4b0107a220068170e8683
Author: Goutham Pacha Ravi <email address hidden>
Date: Mon Mar 7 20:06:50 2016 -0500

    Disallow scheduling multiple replicas on a given pool

    Currently, while scheduling a new replica, the ShareReplicationFilter
    passes any host that shares the replication_domain of the active
    replica's host. On successive runs on the CI, it was observed
    that the same host was chosen multiple times. In a real
    deployment, there is no practicality in allowing replication
    within the same pool.

    Pass more information to assist the filter in disqualifying hosts that
    already host replicas for the share.

    Also treat NoValidHost exception differently from other scheduler
    exceptions to be consistent with other scheduling failures.

    Change-Id: Iedc7b752c7fc477d6257d100e2277378d59f1fde
    Closes-Bug: #1554282

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/manila 2.0.0.0rc1

This issue was fixed in the openstack/manila 2.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 2.0.0

This issue was fixed in the openstack/manila 2.0.0 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.