||Dependency View takes 5 minutes or more to load.
||Component graphs show internal ID instead of hostname.
||Once the device tree contains a minimal set of sub-organizers (Devices, Groups,
Systems, Locations), the auto-refresh is slow. While the tree is being retrieved, the
entire tree becomes blank and displays a loading message.
||Graph range for 'Yesterday' is actually the last 24
||Projected values are not being displayed.
||Resource Manager will allow duplicate IPs for a device.
|ZEN-27096 / ZEN-27291
||When filtering on production state AND sorting other fields on the Infrastructure
page, a ProdStateNotSetError flare is displayed.
||MultiGraph reports display last group name for all graphs.
||The Device component list in the Resource Manager UI is not sorted
||Model Collection Age displays epoch time instead of "Not
Modeled" for devices that are not modeled.
|ZEN-27211 / ZEN-27230 / ZEN-27380
||Service definitions should be consistent between fresh and upgraded
||Unable to ack or close events within the Infrastructure page.
||OS Process Monitoring (SNMP) can send duplicate events if the component has been
||Uninstalling a ZenPack that has a service results in a traceback error.
||By default, zauth zserver-threads are set to 10.
||No event is raised when SNMPv3 modeling fails with a traceback.
||Graph export file (CSV) does not have any unit of measure.
||ZenPacks are not always installed in the correct order during Resource Manager upgrade.
||When a backup is taken while the system has a large number of DB writes
happening, the restore from the backup may result in database corruption.
||Zenoss toolbox should be included in the product image.
||In appliance install, an upgrade of Control Center on delegates from
version 1.3.0 to 1.3.x does not complete.
||With component groups containing vSphere pNICs, many will have the same name. the
user will not be able to tell which pNIC goes with which host, or which vNIC with