topic Re: BUG: Source zone is removed when editing a security policy in Expedition Discussions

BUG: Source zone is removed when editing a security policy

AaronFaby — Wed, 19 Dec 2018 19:26:36 GMT

Hi all,

Using version 1.1.1. I noticed that when I am editing a security policy it will usually remove one of the source security zones. It appears that if there is more than one source zone this happens, not if there is a single zone listed.

Can someone else confirm?

Thanks!

Re: BUG: Source zone is removed when editing a security policy

bagherib — Thu, 20 Dec 2018 01:26:43 GMT

Was it an ASA Import?

Re: BUG: Source zone is removed when editing a security policy

sjanita — Thu, 27 Dec 2018 09:03:41 GMT

Are you using a Panorama configuration? I am seeing similar behavior in Panorama configurations that have templates, but the templates do not have any interfaces or virtual router configurations. Can you check if your configuration file is a Panorama configuration and has templates with no interfaces and virtual router configurations?

Fyi, I am not seeing this behavior with Panorama configurations that have templates with interface and virtual router configurations.

Re: BUG: Source zone is removed when editing a security policy

dgildelaig — Mon, 31 Dec 2018 18:56:47 GMT

Are you sure it deletes them?

Could it be that it presents them in a different order?

I tried to replicate the issue, but I did not have this behavior that you mention.

Re: BUG: Source zone is removed when editing a security policy

bagherib — Mon, 31 Dec 2018 19:55:53 GMT

I couldn't replicate it either.

I've seen this happen when I tried to edit a bunch of rules and Expedition was still processing it and I made a change. I lost 900+ source zones. I learned to wait for Expedition to process the multi-edit selection.

I too noticed (and reported it to this community) that the rules are not being ported in order as they are in the ASA.

Bob

Re: BUG: Source zone is removed when editing a security policy

dgildelaig — Wed, 09 Jan 2019 11:08:53 GMT

Thanks for reporting.

We finally found the reason and it will get resolved in the next update.

There was a UI issue that would miss reading some zones if the back-end would take to long to respond with them.