Renaming is not supported after upgrade from 16.1 17.1

[nunofabarros]

Environment

• Application Services Version: 3.49.0
• BIG-IP Version: 17.1.1.1 Build 0.21.2 Enginerering HotFix

Summary

After upgrading from 16.1 to 17.1 submitting a new AS3 is failing the following error: Renaming /Common/Shared/Service_Address-0.0.0.0 to /Common/Shared/Service_Address-any is not supported

Steps To Reproduce

Steps to reproduce the behavior:

1. Submit the following declaration:

{        
   "class": "ADC",
   "schemaVersion": "3.25.0",
   "id": "urn:uuid:xxxxxxxxxxxxxxxxxxxxx",
    "updateMode": "selective",
    "Common": {
          "class": "Tenant",
          "Shared": {
              "class": "Application",
              "template": "shared",
...
              "vs_http_to_https_redir": {
                                  "layer4": "tcp",
                                  "iRules": [
                                      "https_redirect_gcp_healthCheck"
                                  ],
                                  "source": "0.0.0.0/0",
                                  "translateServerAddress": true,
                                  "translateServerPort": true,
                                  "class": "Service_HTTP",
                                  "profileTCP": {
                                      "bigip": "/Common/f5-tcp-progressive"
                                  },
                                  "profileHTTP": {
                                      "use": "http_sde"
                                  },
                                  "persistenceMethods": [],
                                  "virtualAddresses": [
                                      "0.0.0.0"
                                  ],
                                  "virtualPort": 80,
                                  "snat": "none",
                                  "allowVlans": [
                                      "external"
                                  ]
                              },
                              "vs_https_default_responder": {
                                  "layer4": "tcp",
                                  "iRules": [
                                      "http_sorry_page"
                                  ],
                                  "source": "0.0.0.0/0",
                                  "translateServerAddress": true,
                                  "translateServerPort": true,
                                  "class": "Service_HTTPS",
                                  "serverTLS": "clientssl_sde",
                                  "profileTCP": {
                                      "bigip": "/Common/f5-tcp-progressive"
                                  },
                                  "profileHTTP": {
                                      "use": "http_sde"
                                  },
                                  "persistenceMethods": [],
                                  "virtualAddresses": [
                                      "0.0.0.0"
                                  ],
                                  "virtualPort": 443,
                                  "snat": "none",
                                  "redirect80": false,
                                  "allowVlans": [
                                      "external"
                                  ]
                              },

...

    }
}

2. Observe the following error response:

{
    "message": "Renaming /Common/Shared/Service_Address-0.0.0.0 to /Common/Shared/Service_Address-any is not supported",
    "host": "localhost",
    "tenant": "Common",
    "code": 422
}

Expected Behavior

Expected the AS3 POST to be submitted successfully

Actual Behavior

AS3 POST failure with error 422

Found workaround

Deleting the Virtual Servers at /Common/Shared and submitting again the AS3 is successful, But there is the downside that deleting the virtual servers causes a temporary downtime that wasn't need before.

Thanks for the help.

Best regards,

Nuno

[sunitharonan]

Please reach out to us at [email protected] in order for us to prioritize. Thanks.