There appears to be a pretty serious issue with installing Adobe CC packages via Munki on the Catalina Beta.
Installation generally fails except in this specific scenario:
1) Machine is at the loginwindow
2) You ssh in and run `managedsoftwareupdate` (to download the installer), then `managedsoftwareupdate --installonly` (to install it).
It fails if someone is logged in, or if one of the "normal" workflows at the loginwindow (which is similar to running it with `managedsoftwareupdate --auto`) is used.
It also fails if you run `managedsoftwareupdate --auto` at the loginwindow.
That's perplexing, because the _exact same installer code_ runs via `managedsoftwareupdate --installonly` and `managedsoftwareupdate --auto` -- the only difference I can think of is that `managedsoftwareupdate --auto` at the loginwindow causes MunkiStatus to be launched.
As an additional experiment I modified the pkginfo for an Adobe CC installer, removing the "installer_type" key and value. This causes Munki to bypass all of the Adobe-specific installation code, and just use `/usr/sbin/installer` to install the package. Success and failure follows the same patterns as when Munki calls the Adobe installer tools directly instead of using /usr/sbin/installer to install the package.
I find this issue very difficult to understand. Adobe's logging isn't a lot of help. (At the loginwindow, the relevant log is in /var/root/Library/Logs/PDApp*.log; if there is a GUI user the relevant logs are in the _current GUI user's_ home (yes, even though Munki is installing as root).
In a successful install, you'll see a bit like this:
09/03/19 15:54:19:102 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1530014 | Bootstrapper launch location is :: /Volumes/Photoshop CC (20.0.4)_Install/Photoshop CC (20.0.4)_Install.pkg/Contents/Resources//ASU2/Install.dylib/Contents/MacOS/Install
09/03/19 15:54:19:105 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1530014 | Build Version - 1.15.0.68
09/03/19 15:54:19:105 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1530014 | Logging Level verbosity Set to 4
09/03/19 15:54:19:105 | [FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 1530014 | Failed to launch the Bootstrapper process.Stopping the installation process.
09/03/19 15:54:19:105 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 1530014 | CCP ASU installation failed with ErrorCode (81). Ignoring this ASU failure.
Note that even though there is a "FATAL" entry which claims it will be "Stopping the installation process" the install continues and is successful.
For an installation failure, the log starts the same way, but we get a different FATAL line:
09/04/19 21:22:57:087 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1840356 | Bootstrapper launch location is :: /Volumes/Photoshop CC (20.0.4)_Install/Photoshop CC (20.0.4)_Install.pkg/Contents/Resources//ASU/Install.dylib/Contents/MacOS/Install
09/04/19 21:22:57:209 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1840356 | Build Version - 1.15.0.68
09/04/19 21:22:57:209 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 1840356 | Logging Level verbosity Set to 4
09/04/19 21:22:57:209 | [FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 1840356 | The Bootstrapper Process return code is (6).Stopping the installation process.
09/04/19 21:22:57:209 | [INFO] | | ASU | DeploymentManager | AAMEEUtilities | | | 1840356 | Preffered languages returned from the OS api call (en)
And in this case, the installation is really aborted.
So the key is -- what is causing the Bootstrapper Process to return code 6?
But my best guess is that there is some other process running that the "Bootstrapper Process" doesn't like. But the logging doesn't help us know what that might be.
-Greg