F5Networks / f5-appsvcs-extension

F5 BIG-IP Application Services 3 Extension
Apache License 2.0
163 stars 52 forks source link

profileTrafficLog": not working together with "class": "Service_L4", #792

Open DahlPatric opened 5 months ago

DahlPatric commented 5 months ago

Environment

Summary

profileTrafficLog together with Service_L4 result in error, not able to implement

Steps To Reproduce

Steps to reproduce the behavior:

  1. Submit the following declaration:

    "MyTenant": {
      "class": "Tenant",
      "Application": {
        "class": "Application",
        "template": "generic",
        "MyApplication": {
          "class": "Service_L4",
          "virtualPort": 6443,
          "virtualAddresses": [
            "192.168.1.10"
          ],
          "layer4": "tcp",
          "profileL4": {
            "bigip": "/Common/fastL4"
          },
          "profileTrafficLog": {
                "bigip": "/Common/request-log"
            }
        }
      }
    }
  2. Observe the following error response:

    {
    "code": 422,
    "errors": [
        "/MyTenant/Application/MyApplication: # is NOT valid"
    ],
    "declarationFullId": "",
    "message": "declaration is invalid"
    }

Expected Behavior

"Code": 200

RobCupples commented 5 months ago

If you create a Service_L4 and look at it in the BIG-IP GUI you will see it is a virtual server of type "Performance (Layer 4)". I have never been able to attach a traffic log to this server type in the GUI or TMSH.

I have presumed it is because a traffic log is too Layer 7 and incompatible with this server type so the BIG-IP does not allow it. If you know a way and can share it we can look into adding it.

DahlPatric commented 5 months ago

You probably right, should it then be removed from schema-reference? https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/refguide/schema-reference.html#service-l4

RobCupples commented 5 months ago

Thank you for pointing that out. It should not be in the schema reference.

This issue is being tracked internally with the id AUTOTOOL-4151. I will see that it gets directed towards fixing the schema reference.