topic Re: 4.0.8 Object Name Change Not Updated In Policy in General Topics

4.0.8 Object Name Change Not Updated In Policy

rob.burgoyne — Tue, 17 Jan 2012 00:31:25 GMT

I used to be able to make changes to objects (address/groups/application groups) ect. But now when I made the change I have to go through my policies and NATs and update them manually. Any ideas? Is there an update object option that I'm not aware of?

Re: 4.0.8 Object Name Change Not Updated In Policy

spolo — Tue, 17 Jan 2012 04:11:58 GMT

I think I might be confused by your question. Are you saying that when you go to the Objects tab > Addresses (for example) and you modify an address object's name, it does not modify that in the security rule? Don't have a box running 4.0.8 right now, but tested in 4.0.4 and 4.1.1 and objects do get renamed properly there.

Is it possible you're using Panorama and you're renaming shared objects and not localized objects or vice versa?

Re: 4.0.8 Object Name Change Not Updated In Policy

rob.burgoyne — Tue, 17 Jan 2012 04:34:02 GMT

Yes exactly, its really annoying and I only started seeing it after we upgraded to 4.0.8. It doesn't change the object in the NAT, ACL, or Address Groups. You litereally have to go to each one and re-enter the correct name. Otherwise you get an error when trying to commit that says no refrence found for XX. I have about 150 objects that need to have their names changed with our new standard...

Re: 4.0.8 Object Name Change Not Updated In Policy

spolo — Tue, 17 Jan 2012 05:58:29 GMT

I think it would be best to call in to support on this issue and have them look at it. If necessary, they can have engineering look at it as well.

Re: 4.0.8 Object Name Change Not Updated In Policy

licenselu — Wed, 18 Jan 2012 20:08:55 GMT

Hello,

I can confirm this bug 4.0.8 (cluster of PA500).

Regards,

Hedi

Re: 4.0.8 Object Name Change Not Updated In Policy

stefan_h — Thu, 19 Jan 2012 15:52:20 GMT

Hi all,

same here since upgrading our PA2020 cluster to 4.0.8.

Is there an official statement / confirmation from PA on this issue?

Regards Stefan

Re: 4.0.8 Object Name Change Not Updated In Policy

spolo — Thu, 19 Jan 2012 17:07:02 GMT

I'm not at a place where I can test this now, but standard practice in situations such as these is to open a case with support to get this into the right hands as quickly as possible. If you open it online, outline the steps to re-create the issue. The support engineering team can either come up with a fix or a work-around, and if it's a bug then they can file it as such in our bug tracking system. The development engineering team will then assign to the appropriate engineers teams for a fix. Opening a case allows you to follow this progress and communicate with the assigned support engineer.

So in that light, I'd recommend opening a case to get the right people on it ASAP.

Re: 4.0.8 Object Name Change Not Updated In Policy

MGoodnow — Mon, 23 Jan 2012 14:16:58 GMT

Same issue here (4.0.8). Modify any object in the "Objects" tab - and the corresponding policy does not get the change (commit fails with "device: failed to find address....."). Process is to then go hunt down where the object is used - delete it and then re-add back to the policy.

- mike

Re: 4.0.8 Object Name Change Not Updated In Policy

bryan — Wed, 25 Jan 2012 09:41:19 GMT

Hello All,

This appears similar to a fix which has been included in PanoS v4.0.9 (released 01/23). Reference the list of addressed issues, #35919 which includes a detailed description.

Regards,

Bryan

Re: 4.0.8 Object Name Change Not Updated In Policy

AlesDener — Fri, 09 May 2025 11:19:27 GMT

13 years later and this still hasn't been fixed...

Re: 4.0.8 Object Name Change Not Updated In Policy

kiwi — Fri, 09 May 2025 12:28:34 GMT

Hi @AlesDener ,

This was fixed 13 years ago in 4.0.9.

Instead of reopening a 13y old thread I'd recommend creating a new one as the PAN-OS versions from that time are no longer relevant.

While you're at it, also add some more context of what you're trying to do exactly and on what OS version you're seeing the issue.

Kind regards,

-Kim.