04-26-2022 03:53 PM
The auto commit is essentially what gives your box a valid configuration upon start-up. Without that finishing your box doesn't actually have an active configuration, the GUI is just displaying the candidate-config. When you run show jobs id 1 what's the actual status detail for the job?
Steps I would personally take:
1. Since you have a pending autocommit and not a failed commit, you can just try restarting the box and see if it happens again. If it starts up normally then all is good.
2. If it hangs in pending again, you can try clearing the job clear job id 1 and running commit force to see if that actually commits successfully.
3. If none of that works, take a technical support dump and download it so you have the logs to analyze for the failure. Then open a ticket with TAC.
If you can't wait for this device to be operational, you can always revert to the previous partition to "undo" the upgrade.
1. Run debug swm status and make sure that sysroot0 or sysroot1 is in the REVERTABLE state. The other should show as RUNNING-ACTIVE.
2. Run debug swm revert to go back to the previous partition so the device is at least functional again.
Since your new to PAN, it probably isn't a bad idea to list out how you did the upgrade procedure either (from what version to 10.1.4 did you upgrade, what was your upgrade path?). It's possible that you did something improperly in the upgrade that can cause autocommit issues.
