*.recon become none accessible after unit test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
New
|
Undecided
|
Unassigned |
Bug Description
If we run the unit test in a swift installed environment,the *.recon files may become none accessible.
1、Before the unit test,the owners of there files are swift
ll /var/cache/swift/
total 12
-rw------- 1 swift swift 461 Jan 22 10:50 account.recon
-rw------- 1 swift swift 506 Jan 22 10:50 container.recon
-rw------- 1 swift swift 1616 Jan 22 10:50 object.recon
2、After we run the unit test with some other user such as root,we get a change of these files
ll /var/cache/swift/
total 12
-rw------- 1 root root 462 Jan 22 11:02 account.recon
-rw------- 1 root root 545 Jan 22 11:04 container.recon
-rw------- 1 swift swift 1614 Jan 22 11:04 object.recon
3、And then these files are none accessible to those swift service,we will see some error messages in the swift log file
Jan 21 04:04:27 yanweitest1 container-server: Exception dumping recon cache: #012Traceback (most recent call last):#012 File "/usr/lib/
Jan 21 04:04:38 yanweitest1 account-server: Exception dumping recon cache: #012Traceback (most recent call last):#012 File "/usr/lib/
Jan 21 04:04:49 yanweitest1 object-server: Exception dumping recon cache: #012Traceback (most recent call last):#012 File "/usr/lib/
Although,the scene that running unit test in the same node with the swift installation is unfrequent.But I think if we do some improvements to the unit test cases ,we will save a little time of those guys who encounter this situation.