Unreproducible Issues

Getting Ready › Release Notes › Known Issues and Important Notes › Known Issues and Limitations › Unreproducible Issues

Unreproducible Issues

The following issues have been observed in CA AppLogic releases but are extremely difficult to reproduce (if at all) and have only been observed once or twice. If any of these issues appear on your grid, please send a bug report to CA describing which problem occurred and which CA AppLogic commands were executed that led to the failure.

Defect SCR 2842 - Server rebooted due to a crash in the Linux kernel (observed in various releases)
A server in the grid rebooted on its own due to a crash in the Linux kernel in dom0 of the server. This would not cause the entire grid to fail like in previous CA AppLogic releases; but could cause application downtime. In such a case CA AppLogic restarts the appliances that were running on the failed server on other servers in the grid. If this issue is observed on your grid, contact CA Support.
Defect SCR 2834 - Server loses connection to the grid controller
In CA AppLogic 2.4, there have been several cases where a server loses connection to the grid controller and reboots. This causes all of the appliances that were running on the server to be rescheduled on other servers in the grid and can also cause application downtime. It is unknown why the servers are losing their connections to the grid controller.

If the server's connection to the grid controller is dissolved, the server tries to reconnect to the grid controller and if successful, the server remains operational and there is no application downtime. If the server cannot reconnect to the grid controller for one minute, the server is rebooted and application downtime occurs. When a server loses its connection to the grid controller, a message is logged to the dashboard. If this problem is observed, contact CA Support.
SCR 2903 - Volume resize of 4 NTFS volumes executed at the same time failed
On CA AppLogic, resizing 4 NTFS volumes at the same time caused all four volume resize operations to fail. This issue has been observed only once.
SCR 3289 - NASR replication failure was observed when almost out of disk space
While NASR was replicating an 800MB file on a 1GB volume, the NASR appliance became unresponsive. CA is unable to reproduce this issue. If this issue is encountered on your grid, contact CA support.
SCR 3711 - Opening many graphical consoles crashed a server in the grid
User opened six graphical consoles to different windows appliances running on the grid (opened at the same time). Upon opening the seventh graphical console, one of the servers rebooted and rejoined the grid. The appliances that were running on the failed server were restarted on other servers within the grid. This issue has only been observed once.

BFC Known Problems

We have identified the following known problems with the Backbone Fabric Controller (BFC) in this release:

If you are running a BFC database replica on an NFS hard mounted file system (NFS hard mounts are the default; do not use the optional soft mount functionality), and that NFS-mounted file system fails, the BFC will hang. This issue is a characteristic of NFS itself, and not something the BFC has direct control over. If you end-up in this state and you are unable to restore the NFS file system, you can remove the BFC dependence on that replica to restore normal operation using the following steps:
1. Log in to the BFC system as root.
2. Change to the bfcadmin user by typing the following command:
```
  su - bfcadmin
```
3. Run <BFC install location>/bin/stop_replication (by default, /opt/bfc/bin/stop_replication)
Important! After breaking this dependence, your system will be running without replica, so go back into the UI and establish another replica at the same or a different location.
Do not use the /home/bfcadmin folder for your replica database, or as your download directory for versions, hotfixes, and updates. If you uninstall the BFC, this folder is removed, resulting in the loss of your replica database and other site-owned data.
Defect SCR 6990 - Cannot unset the default VLAN for a grid via the BFC API
Defect SCR 6027 - The grid start from BFC UI fails after it is shutdown using “3t grid shutdown” command
Please do not use the “3t grid shutdown” command on a grid.
Defect SCR 7036 - ESX grid fails due to nfs mount error
When this occurs, doing a “service nfs restart” on the BFC should resolve the problem.
Defect SCR 7058 - Failed ESX grid node goes into an infinite loop of reboot once it is restarted
Defect SCR 6424 -BMI Install prompts for Driver Disk on HP DL360g4p
If you get this message, simply hit the “Esc” key to continue the install.
Defect SCR 7312 - Unattended install fails with password !"$%&/()=?'
If you are performing an unattended install with this version of the product, your password cannot contain a “=”
Defect SCR 7376 - STP check is skipped during network detection if server’s public port is configured as trunk
This bug could occasionally allow servers into grids that should be blocked. If the ports are properly configured, this problem will not be encountered.
Defect SCR 7401 - BFC throws "System_limit" error when total no. of characters in the "Edit Grid Parameters" textbox exceeds 256 characters
If you need to use more than 256 characters, simply break those parameters into more than one update of the grid.
Defect SCR 7818 - Known Issue with Fusion Charts in Internet Explorer 9
If the graphics rendering option is not set correctly in Internet Explorer 9, graphs in the BFC do not display correctly. Affected graphs appear in the BFC Dashboard, Grids, and Servers pages.

To fix this problem, in Internet Explorer 9 click Internet Options on the Tools menu. Click the Advanced tab and locate the Accelerated graphics section. Select the Use Software Rendering check box. Save your changes and restart IE.
Defect SCR 7724 - system with 1000 MACs set to AutoDiscovery (blacklist) mode brings BFC down
If you need to set these many MACs to AutoDiscovery (blacklist) mode, it would be best to use Manual Configuration (whitelist) mode with 3.5.
Defect SCR 7765 - inventory fails when no external IP addresses available
Please ensure you have external IP addresses available when added servers to a BFC.
Defect SCR 7984 - Issues with updation of app IP and controller IP after hitting Reset button
Due to this bug you cannot directly swap the controller and application IPs with each other in one step. If you must do this, first set them to some other values, then you may set them again to the intended values.
Defect SCR 8005 - API: Issues while adding VLAN to the existing untagged grid via API
If you attempt to add a tagged network to an untagged grid via the API, the call will succeed, instead of returning 400 Bad Request.
Defect SCR 8064: Attempting to delete a downloaded but not imported version doesn't give the user any info as to why it doesn't do it
When there is no download server configured (local download directory), we show versions as Downloaded and accept delete operations, but the delete is correctly a non-operation. Future releases will generate an error that describes why this action doesn’t do anything.
Defect SCR 8231: Download error message not clear when selecting to download an already downloaded version
This is not really an error, just a confusing message.
Defect SCR 7815: BFC API allows a vlan to be added to a grid multiple times
You can use the API to add the same range multiple times, but you can use the UI to remove the duplicate ranges. (Leaving the duplicate ranges in place, however, will not case any problems.)
Missing localization strings in BFC 3.7.0
Since 3.7.0 has not been localized, the new parts of the application will only display English strings. The previously localized parts of the application (those that existed in 3.5) will still display the non-English strings as before.
Defect SCR 8452: Some Dell machines will not boot into a grid if the Virtual Media option is enabled in the DRAC
On some Dell hardware you can enable a DRAC Virtual Media BIOS option. This feature allows you to boot from a virtual media device over the network. However, the CA AppLogic kernel may identify the virtual media device as a SCSI device and confuse the boot device name (what was "sda" becomes "sdb").

To avoid this problem, disable the DRAC Virtual Media option in the DRAC BIOS on your Dell hardware.
Defect SCR 8400: BFC service crashes when adding a very large MAC address list to the discovery white list or black list
When you add or remove addresses to the list of MAC addresses in the BFC, limit the maximum number to 500. The MACs list is used in Discovery Mode to include servers (when set to Manual Configuration) or exclude servers (when set to Auto Discovery mode).

You can work with the list of MACs on the Administration page of the BFC on the Discovery tab. You can edit the list of servers, or can import a file with a list of servers. You can also set the MAC address list using the BFC API.
Defect SCR 8036: 3TB disks are not supported for ESX grid servers
While AppLogic Xen grid servers support 3TB disks, AppLogic ESX grid servers support a maximum of 2TB disks. Servers with 3TB disks should not be chosen to run the ESX hypervisor otherwise grid creation will fail.
Defect SCR 8883: BFC Recovery hangs when a previously imported AppLogic version is not available at the configured download server
If you participated in the CA AppLogic 3.7 beta program then you must make sure that the beta version of CA AppLogic is present in your BFC’s download directory if you must execute the fallback procedure due to a failed upgrade.