FGL-19587

Fixed issue where IntegrationAction and IncidentExportAction rules were not listed.

FGL-19578

REST API NPE occurred during the startup of Foglight Management Server, which caused the web console of the Foglight Management Server was not available.

FGL-19547

If the port number of SQL Server was changed during the server upgrade, the upgrade process would be failed.

FGL-19497

Fixed issue where FMS picked up IPv6 address as the host name.

FGL-19454

Fixed issue where UnixAgentPlus agents could not be moved to other FglAM on the Agent Status dashboard.

FGL-19420

Fixed issue where "&&" was not supported for the Run Script REST API.

FGL-19408

Fixed the HTTP Header vulnerability.

FGL-19409

Fixed issue where Chinese characters were not supported for the "Forward Alarms as SNMP Traps" rule.

FGL-19377

Fixed issue where the object-level config was not supported.

FGL-19316

Fixed issue where the "Service back to Normal" email message was kept sending once a minute in the Federation environment.

FGL-19281

Fixed the ZenMap vulnerability.

FGL-19251

If alarms for a service were not cleared, the Foglight Management Server always got these alarm emails after the server was restarted.

FGL-19234

Fixed issue where the Installation Wizard was not shown completely on the SUSE Linux Enterprise Server (SLES) OS.

FGL-19128

Fixed issue where a scheduled report was generated and sent twice via email in the HA environment.

WCF-15913

Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround.

FGL-19479

The Management Server UI will possibly be displayed abnormally if Tomcat version is upgraded.

 Workaround: Clear the cache data of your web browser.

FGL-19431

If you toggled enable/disable state for Alarm Integration, Incident Integration, Clear Integration Alarm, or QMX Agent Host Connection Rule rule in the Integration cartridge, its enable/disable state will be reset after upgrading to 5.9.x from 5.7.5.8. 

FGL-19283

When upgrading the Management Server from 5.7.5.8 to 5.9.x, unexpected CartridgeDeploymentException shows in the log file.

Workaround: This exception only occurs in environments with those cartridges which define Java Archive or JBoss Artifacts component, like Integration and IntelliProfile cartridges. JBoss Server has been removed from the Management Server 5.9.x. As a result, JBossDeploymentHandler, which was used to handle above components, is also removed from the Management Server 5.9.2. If you encounter this issue, you could ignore it as this exception does not impact upgrade of the Management Server and relevant cartridges. 

FoglightShutdownAction.checkInUsedPort() does not load port settings from server.config during an upgrade.

In a Windows Single-Sign ON (SSO) with untrusted multiple domains, only the user with the keytab file-corresponding group can be imported.

The Management Server data-driven multiple severity rules may fire multiple times for the same severity in case of concurrent data submissions.

The rule engine may pass non-persisted alarm IDs to rule actions. This can prevent some alarms, that are generated multiple times against the same scoping object, from firing.

Failing to start the Management Server with the --host=*.*.*.* option due to a failed attempt to start the embedded database.

LDAP users may have to log in twice to get proper role assignments.

Foglight is configured with a list of default ciphers. Some of these ciphers are potentially vulnerable ciphers. A review of the ciphers that will be available in a future release is ongoing.

Workaround: Edit the list of ciphers by completing the following steps:

1. Open the following file for editing:
   • Releases prior to 5.7.1: <FMS_HOME>/server/deploy/jboss-web.deployer/server_https.xml
   • 5.7.1 release and later: <FMS_HOME>/server/tomcat/server.xml
2. In this file, specify a list of ciphers in the ciphers attribute of the secure connector:
   
   <Connector executor="tomcatThreadPool" maxHttpHeaderSize="8192" URIEncoding="UTF-8" scheme="https" secure="true" SSLEnabled="true" clientAuth="false" keystoreFile="../../config/tomcat.keystore" keystorePass="nitrogen" sslProtocol="TLS" sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1" bindOnInit="false" ciphers="COMMA_SEPARATED_LIST_OF_CIPHERS"/>
   

For complete information, visit http://tomcat.apache.org/tomcat-7.0-doc/config/http.html.

The Management Server distribution layout contains some confusing directories under server/jboss.

Core monitoring policy derivations are not deployed on a Federated Master.

Excluded objects are sometimes included in a Federation topology synchronization.

A Foglight Agent Manager that is no longer in use maintains a stale disconnected RemoteObject instance under the host object. This causes the host to appear as undefined on the Hosts dashboard, even though the host is monitored by Foglight for Infrastructure.

When federation.config does not contain any queries, TopologySynchService mistakenly logs the following warning:

WARN Obsolete federated topology object purge will not be performed because the following federated servers are not connected: ...

Topology loading can fail for topology objects that have been converted to DataObjects.

Type-based exclusions in federation.config do not apply to referenced objects.

String observations containing reserved characters in script agents are not supported.

The alarm email notification code does not persist any information about notification alarms that were previously sent. If the server is restarted, all alarms appear as new, and the notifications are resent.

Hibernate/JDBC errors occurring while loading rules return an empty list.

Cleared credential alarms are found when querying for alarms that are not cleared.

Simple rules that report alarms directly are not affected by blackouts.

An attempt to import external groups results in the following error:

Could not execute the requested operation, error(s) had occurred: Failed to retrieve groups, please make sure you correctly configured the Directory Services, check log for details.

The log, however, does not contain any errors.

After changing the value of the registry value, some of the performance calendars may disappear from the list.
Workaround: To correct the display and allow performance calendars to be deleted, return to the main Manage Registry Variables page, then navigate back to the appropriate registry value.

When editing properties from the Agent Status dashboard or the Agent Properties dashboard in Chrome 17, some edit fields are not available.
Workaround: Use a different browser when editing agent properties through these dashboards.

The Cartridge Inventory page is currently unable to alert users if a cartridge install fails due to lack of space in the server's temp directory. An error is written to the log files.

When editing secondary agent property tables from either the Agent Status or Agent Properties dashboards, performing Add and Delete operations at the same time results in all Added items being deleted.
Workaround: Add items to the table, save them, and close the popup window, then edit the secondary property again and delete the rows that need to be deleted. Finally, save and close the popup window. This ensures that the added items remain.

Selections made on the Service Selector tab of the Select services and tiers to monitor dialog box of the SOC become unselected when you switch to the Tier Selector tab and back again.

Credential alarm messages sometimes contain UUIDs for objects related to the alarm.
Workaround: Show the Alarm Detail dialog for these alarms to resolve the objects to identifiable names.

When using a Federation Master that is a newer version than the Federated Child, it is possible to get warnings about missing metrics. This occurs when new metrics have been added to the Federation Master's version. The warnings indicate that the Federated Child does not provide these metrics, and they will cease when the Federated Child is upgraded to the same version as the Federation Master.

When editing secondary agent property lists, the Delete Selected Row(s) button marks the rows to be deleted by graying them out. Save changes must be selected to delete the selected rows. If a required field is blank, then a value must be entered before the row can be marked for deletion.

When reviewing Alarms on a Federation Master, you are able to open a link to view the rule that fired the alarm on the Federated Child. This involves opening the console of the Federated Child. If the Federated Child is of an older version than the Federation Master, an error page is displayed.

Under rare conditions, if the session is allowed to expire while viewing some of the views in the Administration dashboard, the process of logging in again displays the Administration view without any decoration around the side panels.

Workaround: To clear this condition, close the browser. Do not save your session if the browser prompts you to save the last session configuration. Instead, start the browser and log in again.

The column layout on the Agent Status Page does not allow resizing of columns, which can result in the host name appearing truncated.

An error message stating "Error getting value of context entry with key:timeRange" can appear in the logs when using the popup menu on the Origin field of the Alarm Details dialog.

If a Federation Master Server connects to an older version Federated Child, the Federated Child may have some of the objects that are no longer associated with the Management Server Performance Report and Foglight Server Diagnostic views on the Federation Master. This results in some data about the Federated Child being unavailable to this report and views.
Workaround: Go to the Federated Child to view detailed information.

Inconsistency in the number of alerts shown in the "All Alarms Chart" and "Alarm List with Filter" in the Alarms dashboard.

Display all available scoping objects in the condition editor for copied and user-created rules.

On systems with a large numbers of hosts, the Host Table view can be slow to display.
Workaround: Use the hide column feature to hide the sparkline (small graph) columns. This significantly improves the display performance.

Foglight 4 Tabular views generate an error when the time range has "Auto" granularity.

The edit rule definition for an alarm from a Federated Child brings up a page for editing a rule on the Federation Master, rather than for the rule that triggered the alarm. This occurs because it is not possible to perform administration from the Federation Master.

When the user pastes data using right-click > Paste to a box that automatically updates itself (for example, the edit agent properties screen), the user interface does not automatically refresh itself.
Workaround: After pasting into an Agent Properties text field, press the Spacebar > Backspace, and click the Save button.

When agent activation fails, the "Activating" status box does not show the status of the failed start agent.

The Service Levels Details page does not show cleared alarms for Service Level Policy.

Seconds should be displayed in the startTime and endTime in the WCF under Browse > Data when granularity is set to "raw".

QP5 needs to be upgraded to the latest version.

In Internet Explorer 8, when the number of dashboard nodes in the navigation panel exceeds the maximum that can be displayed without a scrollbar, the scrollbar does not immediately appear.

Tree Table list nodes should not be clickable or dwellable.

WCF-7344

PDF charts and files that were requested through a proxy fail and result in a Connection Refused error. Note that this error only applies to requests made by the Management Server.

WCF-5895

Vertical scrollbar not shown for the text area.

The Foglight Management Server generates an "Unable to load Java VM shared library to start JVM" message when attempting to start the Management Server on a Red Hat Enterprise Linux Server 5.0 VMware machine.

This is caused by the SELinux security code on newer RedHat systems. There are two workarounds:

• Enter the following command (as root):
  
  chcon -t textrel_shlib_t <foglight_home>/jre/lib/i386/server/libjvm.so
   

• Disable SELinux on the system in question.

This issue is addressed in the Sun JDK 1.6.0 release notes:
http://www.oracle.com/technetwork/java/javase/6u4-140071.html
Bug: 6538311
This bug affects both Foglight Management Server executables (fms and fmsha).

Installation: Console Mode. Returning to a previous step in the installation process after being prompted for a user password, the input is not recognized.
During a console mode install, it is possible to return to the previous step by typing "back" and then pressing the Enter key. If done while the installer is asking the user to enter a password, all subsequent user inputs are automatically changed to asterisk symbols (* ) and are unreadable by the console.
Workaround: Type quit and reinstall again.

Installation: Console Mode. Some characters of the Administrator's password are not hidden if typed too quickly.
This issue has been observed when installing Foglight on some older machines.
Workaround: Avoid typing the password fast.

When typing words containing "ss" in the online help search, a null pointer exception is generated.
This is a known issue for applications that use Oracle's default implementation of the Java Help Search functionality.