F5Networks / f5-azure-arm-templates

Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
84 stars 118 forks source link

F5 Azure Sync Failed Error #44

Closed cxcal2 closed 6 years ago

cxcal2 commented 6 years ago

Description

Sync failed between F5 HA azure build

"Sync failed

A validation error occurred to a remote device

Sync error on f5name.cloudapp.azure.com> Load failed from /Common/f5name.cloudapp.azure.com 01070712:3. Caught configuration exception (0). Values (/Common/vip_name) specified for virtual server policy (/Common/vip_name /Common/asm_auto_I7_policy_vip_name); foreign key index (vs_FK) do not point at an item that exists in the database.

Recommended action: Review the error message and determine corrective action on the device. f5 azure error

Template

f5-azure-arm-templates (existing network) with 3 NICs and 1 external IP

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: 1

mikeshimkus commented 6 years ago

Hi, this isn't an issue with the ARM template, but rather with BIG-IP configuration. I recommend contacting F5 Support.

cxcal2 commented 6 years ago

Also this was created as BYOL from https://github.com/F5Networks/

cxcal2 commented 6 years ago

Unfortunately this was setup with a two demo licenses as a POC.

mikeshimkus commented 6 years ago

I have seen similar errors before, usually I've had to examine the offending object in bigip.conf and manually make sure the configs match between BIG-IPs.

cxcal2 commented 6 years ago

I found this article describing the same issue we are having in v13. I have attempted the workaround per the recommendations in the article:

https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-hotfix-12-1-1.html

604011-1 : Sync fails when iRule or policy is in use

Could this bug still exist in v13??

cxcal2 commented 6 years ago

I can sync with not problems if I remove the asm policies from the associated VIPs.

cxcal2 commented 6 years ago

Found out this error is an actual bug that did not get fixed in v13.0. Issue is resolved in v12.1

mikeshimkus commented 6 years ago

Great, thanks for the update. Closing this issue as it is not specific to ARM templates.