Upgraded firewall from 9.0.10 to 9.1.13-h3, after which was unable to commit. Confirmed that the version in GUI showed 9.1.13-h3, but downloaded config showed <config version="9.0.0" urldb="paloaltonetworks"> at the top of the xml. show_log_system.txt shows that during the upgrade, autocommit failed, but then succeeded approximately one minute later.
After removing the offending config, was able to successfully commit and exporting the running config showed version 9.1.0.
Is there more that I need to look for than the autocommit to know that the upgrade process is complete?
How was the config synced between HA pairs when one showed 9.0.0 and the other showed 9.1.0?
Thanks in advance for clearing my confusion.
The config that was listed as 9.0 was downloaded a day after the second autocommit succeeded.
I'm just going to chalk this up to weirdness and hope I don't see it again.
You should probably look at this as multiple events that each should be looked into rather than one big issue Why did the first autocommit fail? Was a service not started yet or was there another problem Once the second autocommit succeeded, you should be in a "good place" as this means the config was migrated and committed to system successfully At what point did you download the 9.0 config? Before the last autocommit succeeded or after?