Number of segments/total size aren't listed correctly after upload/delete operations

[Inessa Vasilevskaya]

If a file is uploaded with --segment-size option to a brand-new container, the files number/segments number is updated only on swift list --lh and remains 0/0 on swift list -l command.

Steps to reproduce:
1. swift --os-username services:glance --os-password SOMEPASS upload aaa .viminfo --segment-size 42
In my case the file was uploaded in 127 segments.

2. swift --os-username services:glance --os-password SOMEPASS list -l
 0 0 2015-05-08 16:35:15 aaa
 0 0 2015-05-08 16:35:16 aaa_segments

3. List containers in human-readable format
 swift --os-username services:glance --os-password SOMEPASS list --lh
    1 0 2015-05-08 16:35:15 aaa
  128 5.2K 2015-05-08 16:35:16 aaa_segments

4. Any further calls to list -l will retrieve updated information
swift --os-username services:glance --os-password SOMEPASS list -l
    1 0 2015-05-08 16:35:15 aaa
  128 5353 2015-05-08 16:35:16 aaa_segments

The same inconsistency is observed during delete operation, if the swift delete operation has been aborted (via CTRL+C, for example). In this case swift list -l will show the number of segments present before the deletion.

[Inessa Vasilevskaya (ivasilevskaya)]

I was unable to reproduce the issue on the latest devstack, so I suppose that upgrade of python-swiftclient will fix the problem.

[Alexey Khivin (akhivin)]

The possible reason of such behaviour could be in the fact that glance uses dynamic large object (DLO) manifests. So it is possible to see that some of the segments is not listed right after file successfully uploaded. All of segments should be listed correct after some delay (it depends on cpu usage)

[Timur Nurlygayanov (tnurlygayanov)]

Need to check the issue on MOS 8.0

[Anastasia Kuznetsova (akuznetsova)]

@Maksym, could you please take a look at this bug in 9.0 and if it is still actual that provide more logs/info and assign it to MOS Swift team, otherwise I propose to close this bug as "Invalid" for 9.0

[Dina Belova (dbelova)]

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0