Exit after Preparing

[jeolsen]

Hello, we're seeing the script run and start to run the installer, but after Preparing to a certain percentage it just seems to stop and exit. no other information. Anyone else see this or know of a fix? Happening on Mojave 10.14.6

from startosinstall.log:
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
Preparing to run macOS Installer...
Preparing: 16.8%      

From Jamf log:
Script result: Killing caffeinate processes.
No matching processes were found
Killing startosinstall processes.
No matching processes were found
Killing osinstallersetupd processes.
No matching processes were found
Power Check: OK - AC Power Detected
Disk Check: OK - 633458066440 Bytes Free Space Detected
/Applications/Install macOS Catalina.app found, checking version.
Found macOS installer for version 10.15.7.
Installer found, version matches. Verifying checksum...
Checksum: Valid
Launching jamfHelper as FullScreen...
Running a command as '"/Applications/Install macOS Catalina.app/Contents/Resources/startosinstall" --agreetolicense --nointeraction --pidtosignal 91106 --forcequitapps >> /var/log/startosinstall.log 2>&1 &'...

[jeolsen]

One more update, we are seeing that users who manually run Install macOS Catalina.app are not seeing this issue. I do also have a case open with Apple to see if they can find anything specific in the install.log. But nothing yet.

[manicslothpdx]

I am intermittently seeing a similar issue when attempting to update a Catalina Mac with Big Sur. One time, the % got all the way to 95.3 before stalling. If I open the same installer app locally, it opens within 2-3 seconds.

[jeolsen]

JAMF-1980131 is the Jamf case number if anyone needs it. I was asked to run “sudo '/Applications/Install macOS Catalina.app/Contents/Resources/startosinstall' --agreetolicense --forcequitapps” directly and see if the issue still happens, but haven't had an affected user able to test yet.