Tempest test for dr/readable replication fails because share has two active replicas

Bug #1607150 reported by Goutham Pacha Ravi on 2016-07-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The tempest test:


fails sporadically at the gate for both ZFSonLinux and NetApp cDOT Single SVM drivers because of the update sequence in the share manager.

The test executes only when the backend_replication_type is 'dr' or 'readable'. It performs the following actions:

* Creates a share
* Creates a replica
* Waits for replica to become 'in_sync'
* Promotes the replica
* As soon as the promoted replica becomes available, it requests the list of replicas for the share

At this point, if the share manager is still updating the list of replicas, this operation gets the list of replicas in an inconsistent state. Either, we should wait to get the list of replicas or we should change the order of writing data into the database, i.e, update the promoted replica the last.

Automation might always find such bugs because our API service is uncoordinated from updates from the other services in manila.

Goutham Pacha Ravi (gouthamr) wrote :

Sample failure from NetApp CI attached below.

tags: added: netapp
tags: added: tempest
Goutham Pacha Ravi (gouthamr) wrote :

Sample failure from NetApp CI attached below.

Goutham Pacha Ravi (gouthamr) wrote :
Goutham Pacha Ravi (gouthamr) wrote :
Changed in manila:
importance: Undecided → Low
importance: Low → Medium
Changed in manila:
assignee: nobody → NidhiMittalHada (nidhimittal19)
Tom Barron (tpb) on 2018-06-19
tags: added: replication
tags: added: concurrency
tags: added: races
removed: concurrency
Jason Grosso (jgrosso) wrote :

Goutham how goes this defect? Need any assistance?

Jason Grosso (jgrosso) on 2019-09-19
Changed in manila:
assignee: NidhiMittalHada (nidhimittal19) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers