F5Networks / f5-ansible

Imperative Ansible modules for F5 BIG-IP products
GNU General Public License v3.0
376 stars 231 forks source link

[Request Module] bigip_virtual_server.py #868

Closed minw9545 closed 6 years ago

minw9545 commented 6 years ago
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
2.4.0
PYTHON VERSION
2.7
BIGIP VERSION
12.1.2
LIBRARY VERSIONS
bigsuds==1.0.6
f5-sdk==3.0.18
CONFIGURATION
      - name: "Create Virtual Server"
        bigip_virtual_server:
            description: "Create a LTM Virtual Server for Basic SLB"
            name: "TEST_VS_Asible"
#            partition: "Common"
#            source: "0.0.0.0/0"
#            type: "standard"
#            destination: "50.0.0.53"
#            port: "80"
#            ip_protocol: "tcp"
#            profiles:
#              - "tcp_30M"
#              - "http"
#            snat: "none"
#            enabled_vlans: "all"
#            pool: "TEST_Pool_Ansible"
#            irules: "TEST_Ansile_Rule"
#            address_translation: "yes"
#            port_translation: "yes"
            default_persistence_profile: ""
OS / ENVIRONMENT

N/A

SUMMARY

Our customers are using ansible version v.2.4.0.

Our customer tries the following settings in VS settings.

=> default_persistence_profile: ""

However, this feature is not supported in v2.4.0.

Our customers are reluctant to upgrade.

Can you help me with ansible v2.4.0?

Thank you.

STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS

    "msg": "received exception: Error on setting default persistence profile : Server raised fault: 'Exception caught in LocalLB::urn:iControl:LocalLB/VirtualServer::add_persistence_profile()\nException: Common::OperationFailed\n\tprimary_error_code   : 16908342 (0x01020036)\n\tsecondary_error_code : 0\n\terror_string         : 01020036:3: The requested persist profile (/Common) was not found.'"
wojtek0806 commented 6 years ago

@minw9545 regrettably as far as I know we do not back-port features so this is a no

can you confirm? @caphrim007

caphrim007 commented 6 years ago

@minw9545, @wojtek0806 is correct in that we do not backport things such as this. If you're unable to upgrade ansible in-place, you may want to consider installing it in a virtualenv, container, or separate virtual machine

minw9545 commented 6 years ago

@wojtek0806 @caphrim007 Is it impossible to use this feature with ansible version v2.4.0?
Is there any way to set persistence value to none?

caphrim007 commented 6 years ago

@minw9545 the issue is specific to the "empty" condition.

minw9545 commented 6 years ago

@caphrim007

It is last question

Our customer wants to get rid of the default persistence profile set. Are there other parameter values ​​provided besides "empty"? (ansible v2.4.0)

caphrim007 commented 6 years ago

@minw9545 you can exclude the default_persistence_profile setting and use the bigip_command module with the appropriate tmsh modify ltm virtual command. That will remove the profile. It will be 2 tasks in the playbook, but will have no ill-effect. This would also allow you to work around the problem until such time as an upgrade can be done.

minw9545 commented 6 years ago

@caphrim007 Thanks for your kindly answer.