2008/09/29
The latest stable packaged version of Zenoss Core, version 2.2.4, is now available for download.
Zenoss Core 2.2.4 is available from: http://www.zenoss.com/download.
This is a maintenance release that addresses the following issues, by component:
Notable Notes:
Reboot Appliance After Upgrade
Upon completion of an appliance upgrade from 2.1.X to 2.2.4, you should reboot the appliance as documented in the updated install guide. Otherwise the upgrade may not complete and you will still be running with a back-level kernel. Please consult the documentation for other additional guidance.
Avoid Back-Level kudzu / 2.6.26.5 kernel Combination With Appliance
Most customers who use our appliance package will likely be running with kernel 2.6.24.7. If you have unique requirements that have required you to explicitly upgrade your kernel outside the typical appliance upgrade process, then you may be at risk for an issue that will be resolved under the following ticket: http://dev.zenoss.com/trac/ticket/3788. This ticket discusses the problem and provides information on how to determine if you are at risk for the issue. It also explains how you can work around the problem.
All
- 3568 Only 9 interfaces of a router or switch show up
- 3604 Use "Monitored" checkbox for processes on OS tab
DataCollector
- 3330 Modeling Cisco 7206 crashes Zenhub
- 3553 ZenModeler doesn't model devices in maintenance mode
- 3521 AT&T DS0 Point (64 Kbps) is not a valid interface type name
- 3468 Apply datamap not logging changes
UserInterface
- 3541 Can't override the specifics of a process locally
- 2954 New memory leak on dashboard
- 3500 agent field in event filtering is outdated
- 3416 manual creation of IPService impossible
- 3582 Don't show WinServices on OS tab if zWmiMonitorIgnore is set
- 3620 Bring viewHardDisk template up to speed with latest UI
ZenEvents
- 3549 Users with ZenOperator role can't move events to history from custom event view
- 3467 Make transform readable on event rule
ZenHub
- 3530 Ping topology broken
- 3529 Zendisc error when discovering device that already exists
- 3588 Daemons don't restart cycles after zenhub connection failure
ZenJMX
- 3383 ZenJMX doesn't respond to config deletes and certain config updates
- 3573 ZenJMX does not use parameter values when performing operation calls
- 3649 Stack traces in other ZenPack migrates when ZenJMX ZenPack is present
ZenModel
- 3105 Maintenance windows aren't unindexed on user deletion
- 3485 Network Map doesn't properly deal with nested networks
- 3577 Can't add devices when autodiscovery is off
- 3587 On restart, Zenoss attempts to discover networks that have zAutoDiscover==False
- 3619 TemperatureSensor.name returns invalid response
- 3505 Three unit tests in testDevice.TestDevice fail
- 3469 Handle case delete device without perf collector and don't allow duplicate manage ips
ZenPacks
- 3491 Apostrophe in ZenPack name breaks ability to export
ZenRRD
- 3124 Clean up old data point RPNs that aren't accessible via the UI
ZenRelations
- 3463 zendeviceload fails due to missing import of Globals
ZenReports
- 3486 Include Cisco CPU/Memory in standard performance reports
- 3575 Collection items out of order on multi-graph reports
ZenStatus
- 3564 zenmodeler causes zenping topology to be constantly rebuilt
ZenUtils
- 3585 Utils.unsigned doing bad conversions in InterfaceMap
- 3558 watchdog waits up to 10 hours for a daemon to star
- 3586 running daemons in the forground deletes a background daemon's pid file
