You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The task fails with the below error:
"msg": "CREATE operation error: 1ae1906d-687b-4a57-8bb9-fb98a8e36a3e : [OrchestratorConfigProcessor] Deployment failed for Error: [HAAwareICRDeployProcessor] Error: transaction failed:01070354:3: Self IP 172.23.3.4 / 255.255.255.128: This network is defined on two vlans (/Common/serviceChain1_in and /Common/serviceChain1_out)"
The text was updated successfully, but these errors were encountered:
This same issue seems to be present in the similar module bigip_sslo_service_layer3.
Will this fix also apply to this other module? When using a netmask other than /25 we see the same error message because it is forcing us to use a /25 netmask.
After looking into this some more- I think this is a TMOS limitation. The SSLO auto manage address feature seems to automatically default to /25 netmask and you cannot change it.
Example SSLO UI:
This issue is solved by disabling auto managed address on the service. We have a seperate git issue for that #63 .
If git issue #63 allows us to disable auto manage address and reference an existing self-ip, we wont run into the netmask issue.
COMPONENT NAME
bigip_sslo_service_http
Environment
ANSIBLE VERSION
BIGIP VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 20.04.3
SUMMARY
When using bigip_sslo_service_http module, it cannot create an HTTP service which uses a /28 netmask.
STEPS TO REPRODUCE
EXPECTED RESULTS
Service is created with /28 netmask
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: