Description of problem:
When etcd directory exist for a particular object but it does not have
"data" directory then load_all return an object with some other object
value. For example, there is volume A, B, C then B does not have
data directory then load_all return 3 objects in the list but obj.value is
of A or C is assigned to B is value.
Version-Release number of selected component (if applicable):
This is actually code implementation issue
Steps to Reproduce:
Load all function should return list object with conflict data
Load all function should return list object with its own data
This is code implementation issue
Can you please provide version of selected component and reproducer? For testing purpose it would be good to see example of the data it should/shouldn't return and where to find it.
I don't know where it causes a problem while testing some other bug I saw load_all gives objects with wrong detail. I just fixed this because it may confuse when we debug some other problem. because this will leads to issue which is occurring sometime and sometime it won't raise.
So for make code stable i fixed this problem.
Based on agreement from Bug Triage on 2018-05-10 I provide conditional qe_ack with following assumptions:
* dev team must have done code walkthrough or sanity unit validation of
the change described in this BZ
* qe team will verify this BZ by running general regression tests
This change seems to not break any functionality during testing. Apart from regression tests there were also tested scenarios how tendrl reacts when data directory is removed from etcd. If importing cluster with removed data directory from more clusters then the data directory is generated again and correct cluster is imported. If volume data directory is removed and enable/disable profiling is triggered then the data directory is generated and profiling is enabled/disabled on correct volume.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.