On restart, Zenoss attempts to discover networks that have zAutoDiscover==False

[ian]

A limitation for my project is that Zenoss after a restart is always trying to discover the networks. My client has a class B (e.g 134.111.X.X) and many sites (Chile, Germany) and different usages (isolated network, etc...).

To reproduce : * Add a network 134.111.10.X/24 set auto-discovery to true. * Add a network 134.111.0.0/16 set auto-discovery to false. * Restart zenoss, wait a bit. * 134.171.[1-254].X/24 arer added without my explicit permission.

This result is ICMP storms and it's not good for network health.

I reproduced this on two x86_64 systems running stack 2.2.3. I think the safest wait is to block outgoing ICMP with iptables for the moment.

[bbibeault]

Ian, has this already been fixed?

[ian]

No. This is the next ticket I'll be working on when I have a chance. I have a probable solution, but haven't been able to implement or test yet.

[ian]

(In [9940]) Refs #3587: Creating branch for work on ticket #3587

[ian]

Spoke too soon. This is definitely a valid bug.

[ian]

(In [10011]) Refs #3587/Products: Added unit test recreating error.

[ian]

(In [10012]) Refs #3587: Potential fix.

[ian]

(In [10013]) Refs #3587: Fixed horrible tab characters.

[ian]

(In [10016]) Refs #3587: Basically reverted to r8651 state, plus one change.

[ian]

(In [10017]) Fixes #3587: Merging branch back into trunk.

This change reverses some questionable decisions, causing subnets to be created under their appropriate parent network.
Reviewed by EAD and Chip.

[ian]

(In [10020]) Refs #3587: Backporting r10017 to the zenoss-2.2.x branch

[ecn]

Test case:
Create a /16 network. Add a device with a /24 network under that. Verify that the /24 network is created under the /16 network.

verified on 64-bit sles 10 with enterprise stack .bin installer