Applies To:

Show Versions Show Versions

sol14830: Using an iApp template to create a new application service may cause mcpd to restart on secondary blades
Known IssueKnown Issue

Original Publication Date: 11/26/2013
Updated Date: 04/17/2014

Description

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 BIG-IP system runs on a VIPRION platform configured with one or more secondary blades.
  • You use an iApp template to modify an application service before the system has finished creating the application service.

    For example, an iApp template that triggers this issue may have a set of implementation codes similar to the following:

    tmsh::create / sys application service $object_name
    tmsh::create / ltm pool $object_name load-balancing-mode $lb_method monitor http
    tmsh::create / ltm virtual $object_name destination $listen_port pool $object_name profiles replace-all-with \{http tcp\}
    tmsh::modify / sys application service $object_name strict-updates disabled


    The last line of the implementation code, starting with tmsh::modify, is an example of a command that triggers this issue.

Impact

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.

Symptoms

As a result of this issue, you may encounter the following symptoms:

  • The system creates the new application service on the primary blade.
  • The mcpd process restarts on all secondary blades, which may result in a chassis failover if the system is configured with an HA pair VIPRION chassis.
  • You notice error messages from the mcpd process in the /var/log/ltm log file of the affected secondary blades. The error messages may appear similar to the following:

    err mcpd[9507]: 01020037:3: The requested folder (/Common/myapp-A.app) already exists.
    err mcpd[9507]: 01070734:3: Configuration error: Configuration from primary failed validation: 01020037:3: The requested folder (/Common/myapp-A.app) already exists.
  • After the daemons complete their service restart sequence, the secondary blades return to their operational state.

Status

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
Versions Fixed
Related Articles
Release None None
Hotfix None None

Workaround

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.

Supplemental Information

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)