What steps will reproduce the problem?

(1) At login screen, check /tmp/machine-info contains a non-empty "customization_id" field.

(2) Log in, check /tmp/machine-info file is deleted.

(3) Normally, info private api can still return the correct customization id (https://cs.chromium.org/chromium/src/chrome/browser/chromeos/extensions/info_private_api.cc?sq=package:chromium&g=0&l=290), because statistic_provider cache the customization_id value in memory.

(4) However, if there's browser restart (for example, manually enter chrome://restart), then statistic_provider will not have customization_id, because it reads info from another file (/mnt/stateful_partition/unencrypted/cache/vpd/filtered.txt)