so talking with Gil about this in #opentack-swift it seemed these containers had a container_stat *table* with no object_count field - which is confusing because back when container_stat was a table it always had an object_count field, and post storage policy migration the container_stat table gets migrated to container_info and replaced with a view in a transaction.
Not sure the exact sequence that leads to this state, but it would be nice to verify at a minimum that it will get flagged by container-auditor - which I think maybe it will not (container.auditor.ContainerAuditor.container_audit doesn't seem to rename the db on errors?)
so talking with Gil about this in #opentack-swift it seemed these containers had a container_stat *table* with no object_count field - which is confusing because back when container_stat was a table it always had an object_count field, and post storage policy migration the container_stat table gets migrated to container_info and replaced with a view in a transaction.
Not sure the exact sequence that leads to this state, but it would be nice to verify at a minimum that it will get flagged by container-auditor - which I think maybe it will not (container. auditor. ContainerAudito r.container_ audit doesn't seem to rename the db on errors?)