Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: Jun 29, 2017
When a named node is used as a virtual server destination, several F5 iApps will define the virtual server using the node name rather than the node ip address. This causes the iApp to throw an error and fail deployment.
Virtual addresses are not typically defined as nodes, but in the event that one is, and the specified conditions are met, then the iApp will fail to deploy.
The node is defined prior to running the iApp, it must have a name that does not match its IP address, and its address must be specified as the defined node (i.e., the destination) in the iApp configuration (in this case, f5.http).
Delete the node prior to running the iApp.