Ceilometer pipeline file publisher writes out object references instead of sample content

[Phil Neal]

Enabling the pipeline file publisher generates a file with the following content:

[<ceilometer.sample.Sample object at 0x562d990>, <ceilometer.sample.Sample object at 0x563e990>, <ceilometer.sample.Sample object at 0x563ed50>, <ceilometer.sample.Sample object at 0x563edd0>, <ceilometer.sample.Sample object at 0x563ee50>, <ceilometer.sample.Sample object at 0x563eed0>, <ceilometer.sample.Sample object at 0x563ef50>, <ceilometer.sample.Sample object at 0x563efd0>, <ceilometer.sample.Sample object at 0x3177090>, <ceilometer.sample.Sample object at 0x3177110>, <ceilometer.sample.Sample object at 0x3177190>, <ceilometer.sample.Sample object at 0x3177210>, <ceilometer.sample.Sample object at 0x3177290>, <ceilometer.sample.Sample object at 0x3177310>, <ceilometer.sample.Sample object at 0x3177390>, <ceilometer.sample.Sample object at 0x3177410>, <ceilometer.sample.Sample object at 0x3177490>,

and so on. I'm assuming this isn't expected behavior: as a contrast, the dispatcher file writer pushes out actual content.

Current pipeline.yaml entry:

    name: meter_pipeline
    interval: 600
    counters:
        - "image"
        - "image.size"
    transformers:
    publishers:
        - file:///var/test?max_bytes=10000000&backup_count=5

[Lianhao Lu (lianhao-lu)]

Addressed by https://review.openstack.org/46202

[Julien Danjou (jdanjou)]

This is really funny.