Service_HTTP drops profileL4

[frslater]

Environment

• Application Services Version: 3.23.0
• BIG-IP Version: any

Summary

Specifying "profileL4" inside a service of class "Service_HTTP" is accepted without error, but the profile is not attached. There are 2 problems: (1) AS3 should throw an error, and (2) online documentation (clouddocs) should be corrected, because an example of profileL4 with Service_HTTP is shown as valid.

Steps To Reproduce

Steps to reproduce the behavior:

1. Submit the following declaration:

{
    "class": "ADC",
    "schemaVersion": "3.23.0",
    "id": "TEST_L4_Profile",
    "remark": "Test L4 profiles",
    "L4_Tenant": {
        "class": "Tenant",
        "L4_App": {
            "class": "Application",
            "service": {
                "class": "Service_HTTP",
                "virtualPort": 80,
                "virtualAddresses": ["1.2.3.4"],
                "profileL4": {
                    "use": "l4Profile"
                }
            },
            "l4Profile": {
                "class": "L4_Profile",
                "clientTimeout": 60,
                "idleTimeout": 600,
                "keepAliveInterval": 600,
                "looseClose": true,
                "looseInitialization": true,
                "maxSegmentSize": 4096,
                "resetOnTimeout": false,
                "tcpCloseTimeout": 43200,
                "tcpHandshakeTimeout": 43200
            }
        }
    }
}

2. Observe the following response:

    "results": [
        {
            "code": 200,
            "message": "success",
            "lineCount": 23,
            "host": "localhost",
            "tenant": "L4_Tenant",
            "runTime": 2007
        }
    ]

Expected Behavior

If profileL4 is allowed, then it should be attached to the virtual, but it should probably no be allowed. Assuming it is not allowed, then AS3 should return a validation error.

Actual Behavior

No error is thrown, but the profile is not attached.

ltm virtual /L4_Tenant/L4_App/service {
    creation-time 2021-08-17:07:36:32
    description L4_App
    destination /L4_Tenant/1.2.3.4:80
    ip-protocol tcp
    last-modified-time 2021-08-17:07:36:32
    mask 255.255.255.255
    persist {
        /Common/cookie {
            default yes
        }
    }
    profiles {
        /Common/f5-tcp-progressive { }
        /Common/http { }
    }
    source 0.0.0.0/0
    source-address-translation {
        type automap
    }
    translate-address enabled
    translate-port enabled
}

[frslater]

This bug was originally reported by Aleksandra Zahajkiewicz.

[dstokesf5]

Thank you for your feedback. I have confirmed that a virtual server cannot have a tcp and an l4 profile. The example is being updated and I have added AUTOTOOL-2693 to our internal product backlog to address the lack of validation failure.

[sunitharonan]

If you are still looking for a fix, please reach out to us at [email protected] in order to prioritize.

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.