update_automator_cache infinite loop when building a 10.10.2 NetRestore image with System Image Utility

Number:rdar://20022752 Date Originated:03-Mar-2015
Status:Closed Resolved:
Product:OS X Product Version:10.10.3 (14D87h)
Classification:Crash/Hang/Data Loss Reproducible:Always
On the current (14D87h) developer seed of 10.10.3, attempting to build a NetRestore image of 10.10.2 using System Image Utility results in an infinite loop.

The Essentials install package component contains a postinstall script that calls update_automator_cache, which seems to continue running in an infinite loop, endlessly caching files on the newly-installed filesystem in the temporary volume. This process must be killed manually in order for the installation to complete.

Steps to Reproduce:
1. Download OS X Yosemite (latest at this time is 10.10.2) from the Mac App Store.
2. Open System Image Utility.
3. Select the Install OS X Yosemite (10.10.2, 14C109) source.
4. Select NetRestore image, click Continue.
5. Leave the default settings, create a dummy admin user to allow the process to continue.
6. Choose a target destination for the final output image and start the build.

Expected Results:
Build would normally complete after some time.

Actual Results:
A specific postinstall script causes an infinite loop in the installer process.

com.apple.pkg.Essentials, running the generateCache postinstall_action. The actual process:

/System/Library/Frameworks/Automator.framework/Versions/A/Support/update_automator_cache --system --force

(this is run via `chroot "$3"` to run within the root of the volume that's being installed to.)

This process seems to continue in an infinite loop. Running `opensnoop` confirms that update_automator_cache is still running and reading through files, but this process never exits.

Killing the process allows the installation to continue and complete the image build.

10.10.3, 14D87h

I've verified this on two different systems running this version of OS X. Please let me know if you'd like any additional information.

Two systems tested:
27-inch, Late 2012
Mac Pro, Early 2008


Timothy Sutton - 06-Mar-2015 06:09 PM

Thank you. I realize there's a version mismatch, but since in many cases it "works" to build a lesser point OS version from a more recent point OS version I wanted to confirm whether there might have been an actual issue during the seed period, if there might have been a possibility that 10.10.3 ships and the issue is still present. So this response gives me hope that I don't actually need to be concerned.

Apple Developer Relations - 06-Mar-2015 02:06 PM

There are no plans to address this based on the following:

This is simply not a supported configuration. You should not attempt to mix and match 10.10.3/10.10.2 tools.

We are now closing this report.

If you have questions about the resolution, or if this is still a critical issue for you, then please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!