We recently upgraded to the latest version of Expedition v1.1.14 and there appears to be a bug in the merge/consolidation of service objects. It doesn't matter what we are searching and analyzing - the found results are attempted to be merged and everytime, on every project, we are getting an immediate 'error' - with no additional detail. Oddly enough, even after all the duplicates are found, we can't even manually delete the duplicates.
Analyze service objects with same name - get error on the actual merge.
Analyze service objects with same protcol/port - get error on the actual merge.
This only seems to happen on the merge for service objects specifically.
Solved! Go to Solution.
Where would a log for this type of error be kept? I am poking around different log/debug files but am not finding anything that looks related to a service object merge error.
We are currently in version 1.1.21, in case it has been addressed in recent versions.
Unfortunatelly, I do not think it would be information that gets logged in a tracing file.
If you contact us to fwmigrate at paloaltonetworks dot com, we could try to do a live session to reproduce and diagnose the causes.
We upgraded to verr 1.1.9 and the issue was resolved in that version. We kept upgrading via the standard upgrade script and didn't notice it was erroring out...the error was subtle and at the end it kept saying we were on the most current version so it didn't occur to us that we we were quite outdated. Got that resolved and now its working as expected.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!