Original Publication Date: 11/26/2013
Updated Date: 02/25/2016
Using an iApp template to create a new application service may cause mcpd to restart on secondary blades.
This issue occurs when all of the following conditions are met:
The mcpd process on the secondary blades restarts and traffic may be interrupted. If the affected system is configured with a high-availability (HA) pair VIPRION chassis, the system may fail over to the secondary chassis.
As a result of this issue, you may encounter the following symptoms:
err mcpd: 01020037:3: The requested folder (/Common/myapp-A.app) already exists.
err mcpd: 01070734:3: Configuration error: Configuration from primary failed validation: 01020037:3: The requested folder (/Common/myapp-A.app) already exists.
F5 Product Development has assigned ID 430362 to this issue. F5 has confirmed that this issue exists in the products listed in the Applies To box, located in the upper-right corner of this article. For information about releases or hotfixes that resolve this issue, refer to the following table:
|Type of Fix||Fixes Introduced In||Related Articles|
There is no workaround for this issue.
To avoid this issue, you can reconfigure the iApp template to avoid modifying an application service while the system is still creating the object.
Using the example from the Description section, you can remove the offending line from the iApp template implementation code and then perform any required modification on the properties of the application service using iControl or another script that calls out the appropriate Traffic Management Shell (tmsh) commands.