Zenoss Core Release Notes Release 5.0.10 Zenoss, Inc. www.zenoss.com Zenoss Core Release Notes Copyright © 2016 Zenoss, Inc. All rights reserved. Zenoss and the Zenoss logo are trademarks or registered trademarks of Zenoss, Inc., in the United States and other countries. All other trademarks, logos, and service marks are the property of Zenoss or other third parties. Use of these marks is prohibited without the express written consent of Zenoss, Inc., or the third-party owner. Flash is a registered trademark of Adobe Systems Incorporated. Oracle, the Oracle logo, Java, and MySQL are registered trademarks of the Oracle Corporation and/or its affiliates. Linux is a registered trademark of Linus Torvalds. RabbitMQ is a trademark of VMware, Inc. SNMP Informant is a trademark of Garth K. Williams (Informant Systems, Inc.). Sybase is a registered trademark of Sybase, Inc. Tomcat is a trademark of the Apache Software Foundation. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. All other companies and products mentioned are trademarks and property of their respective owners. Part Number: 1001.16.050 Zenoss, Inc. 11305 Four Points Drive Bldg 1 - Suite 300 Austin, Texas 78726 2 About this document About this document Zenoss Core Release Notes contains important information about minor and micro releases of the following products: ■ Zenoss Control Center (Control Center) ■ Zenoss Core Scope This document provides information about the following releases of Control Center and Zenoss Core: Date Control Center Zenoss Core 19 Feb 2016 1.0.10 5.0.10 02 Dec 2015 1.0.9 5.0.9 16 Nov 2015 1.0.8 5.0.8 13 Oct 2015 1.0.7 5.0.7 15 Sep 2015 1.0.6 5.0.6 07 Aug 2015 1.0.5 5.0.5 13 Jul 2015 1.0.4 5.0.4 27 May 2015 1.0.3 5.0.3 20 Apr 2015 1.0.2 5.0.2 03 Apr 2015 1.0.1 5.0.1 24 Feb 2015 1.0.0 5.0.0 3 Zenoss Core Release Notes Supported clients and browsers The client operating systems and web browser combinations supported in this release. ® ® ■ All browsers must have Adobe Flash Player 11 installed, or a more recent version. ■ Compatibility mode is not supported in Internet Explorer. Client OS Supported Browsers Windows 7 and 8.1 Internet Explorer 11 (enterprise mode is supported) Internet Explorer 10 Firefox 30 and above Chrome 30 and above Windows Server 2012 R2 Firefox 30 Chrome 36 Macintosh OS/X 10.9 Firefox 30 and above Chrome 36 and above Ubuntu 14.04 LTS Firefox 30 and above Chrome 37 and above Red Hat Enterprise Linux 6.5, Firefox 30 and above CentOS 6.5 Chrome 37 and above 4 Feature changes Feature changes Features 1.0.10 / 5.0.10 No new features are included in this release. Note If you are running RHEL/CentOS 7.0, you must upgrade to RHEL/CentOS 7.1 to use this release. The Zenoss Core Upgrade Guide provides upgrade procedures for 1.0.10 / 5.0.10 and RHEL/CentOS 7.1. Features 1.0.9 / 5.0.9 No new features are included in this release. Note If you are running RHEL/CentOS 7.0, you must upgrade to RHEL/CentOS 7.1 to use this release. The Zenoss Core Upgrade Guide provides upgrade procedures for 1.0.9 / 5.0.9 and RHEL/CentOS 7.1. Note If you are running 1.0.8 / 5.0.8 (or earlier), you do not need to upgrade to 1.0.9 / 5.0.9 immediately. However, when you are ready to upgrade, you must follow the steps in the Zenoss Core Upgrade Guide to pull the new images from Docker. Features 1.0.8 / 5.0.8 No new features are included in this release. Features 1.0.7 / 5.0.7 No new features are included in this release. Features 1.06 / 5.0.6 In Control Center, the organization of services in the Zenoss.core appliction is changed. Previously, essential services such as ZooKeeper, HBase, and MariaDB, were in different locations in the application hierarchy. With this release, essential services are grouped into the Infrastructure hierarchy in Control Center, and all other services are grouped in the Zenoss hierarchy. Zenoss recommends shutting down only the services in the Zenoss hierarchy. Features 1.0.5 / 5.0.5 ■ Provided a service definition in Control Center to run the ZenMail service. ■ Configuration steps for monitoring devices on an IPv6 network have been provided for this release. For more information, refer to Notes 1.0.5 / 5.0.5 on page 17. Features 1.0.4 / 5.0.4 ■ A new document is available, the Zenoss Core Upgrade Guide. The Zenoss Core Installation Guide no longer contains upgrade information. ■ Control Center now requires that Docker use the devicemapper storage driver for its images, which are stored at /var/lib/docker. Previously, the btrfs storage driver was required on RHEL and CentOS systems, and the aufs storage driver was required on Ubuntu systems. 5 Zenoss Core Release Notes In addition, Control Center now requires a separate file system for /var/lib/docker. Previously, a separate file system was not required on Ubuntu systems. For more information about the changes, refer to the Zenoss Core Upgrade Guide and the Zenoss Core Installation Guide. Features 1.0.3 / 5.0.3 ■ No new features, only fixed issues in this release. Features 1.0.2 / 5.0.2 ■ No new features, only fixed issues in this release. Features 1.0.1 / 5.0.1 ■ An option to clone an existing service has been added to the serviced command. For more information, log in to the Control Center master host as user with serviced privileges and enter serviced service clone --help at the command line. ■ Product-specifc upgrade scripts, which automate the backend upgrade tasks, are included in the new product images. For more information, refer to the Zenoss Core Installation Guide. Features 1.0.0 / 5.0.0 ■ Zenoss Core is now installed and managed from Control Center. The Control Center is built on Docker, an open-source platform that uses virtual containers to simplify the packaging, installation and management of applications. Control Center provides both a web-based user interface and the serviced command line option. For more information, refer to the Control Center online help. ■ Zenoss Core daemons now run within individual, virtual Docker containers. Containers are light-weight operating environments that contain everything required for an application to run. ■ Zenoss Core daemons can now run on any host in resource pool. They are no longer anchored to a specific host. ■ Performance metrics are now stored in OpenTSDB and HBase instead of RRD Files. ■ Log files are now collected by Logstash and stored in an ElasticSearch database for improved viewing and searching. ■ OpenJDK replaces Oracle JRE. ■ Backup and restore is now performed across the entire application. In previous versions, backups could only be run on the master server or a specific collector. ■ Graphs are now dynamically rendered using a JavaScript library (NVD3.js). 6 Fixed issues Fixed issues Fixed 1.0.10 / 5.0.10 ID Description CC-1873 HTTPS sessions are vulnerable. CC-1911/ Internal UI port 7878 is externally accessible. CC-1914 ZEN-16676 Blank view when navigating to nodes on network map. ZEN-19362 Loading some mibs will succeed; however, parsing will find no entries due to being unable to find dependent mib information. ZEN-20716 Editing a Product (Manufacturers Router) Fails Due to Bad Audit Logging Input. ZEN-21018 Device class /ping status is always unknown. ZEN-21062 Maintenance windows with large number of devices can fail on a zodb conflict error. ZEN-21091 On hubs, allow pingPerspective to be enable/disabled through configuration (‘—ping- perspective’). ZEN-21092 ZenossInfo.getZenossRevision() calls os.popen("svn info"). ZEN-21133 Users other than Admin Cannot Update Triggers and Notifications ZEN-21150 ZenMail does not support Content-Transfer-Encoding Base64. ZEN-21387 ZenManager cannot create trigger or notification. ZEN-21581 When entering LDAP group information, a flare "Type Error: getAvailableLDAPGroup()..." is displayed. ZEN-21583 A device added via UI (zendisc) will model. ZEN-21728 Maintenance Windows Use UTC. ZEN-21801 A graph, containing too many series, cannot be accessed directly via link. ZEN-21843 The Groups, Systems, and Event fields are not sortable by ascending or descending order. ZEN-21917 Tracebacks are generated in zenhub log when performing a collection. ZEN-22013/ Zenpack installation performance has been improved. CC-1935 Fixed 1.0.9 / 5.0.9 ID Description CC-1510 serviced crashes when attempting to configure a collector. CC-1555 Even though all of the healthchecks have passed, Control Center Logstash container is down. CC-1591 Control Center has been updated to support Docker 1.8.2. ZEN-19002 FileSystem transform does not work properly in Zenoss Core 5 because evt.eventKey no longer contains the same datapoint name as in 4.2.x ZEN-20684 ZenPop3 is not available as a service. 7 Zenoss Core Release Notes ID Description ZEN-20969 Page Type notifications are available for creation even though zensnpp has been removed. ZEN-21026 All Zenpacks show passwords in certain URLs. ZEN-21032 Incorrect components are displayed when searching devices in Impact. ZEN-21057 Zenoss Core updated to provide health check for zenmail. Fixed 1.0.8 / 5.0.8 ID Description CC-1435 HTTPS sessions are vulnerable to the POODLE attack CC-1522 Distributed Storage is failing on containers, leading to the container shutting down ZEN-19229 When loading the LDAP settings page in Zenoss Core, the page will hang or in some cases cause zope to fail if the User Base DN structure is large.