No synchronization when AS3 reports "no change"

[erjac77]

trafficstars

Environment

• Application Services Version: 3.13.1
• BIG-IP Version: BIG-IP 13.1.1.4 Build 0.0.4 Point Release 4

Summary

When AS3 reports "no change", the devices won't sync and a "Changes Pending" is triggered, even if the syncToGroup option is set. See issue #207.

Steps To Reproduce

Steps to reproduce the behavior:

1. Submit the following declaration:

{
  "class": "AS3",
  "action": "deploy",
  "persist": true,
  "syncToGroup": "/Common/MyDeviceGroup",
  "declaration": {
    "class": "ADC",
    "schemaVersion": "3.0.0",
    "label": "Sample 01",
    "remark": "Simple HTTP application with round robin pool",
    "sample01": {
      "class": "Tenant",
      "defaultRouteDomain": 0,
      "Application_1": {
        "class": "Application",
        "template": "http",
        "serviceMain": {
          "class": "Service_HTTP",
          "virtualAddresses": ["10.0.1.11"],
          "pool": "web_pool"
        },
        "web_pool": {
          "class": "Pool",
          "monitors": ["http"],
          "members": [
            {
              "servicePort": 80,
              "serverAddresses": ["10.1.2.101", "10.1.2.102"]
            }
          ]
        }
      }
    }
  }
}

2. Observe the following response:

        {
            "message": "no change",
            "host": "localhost",
            "tenant": "sample01",
            "runTime": 557,
            "code": 200
        }

3. Observe the sync status on the BIG-IP: Changes Pending

Expected Behavior

The devices should sync, even if AS3 reports "no change", cause some internal data are changed and stored in data groups.

Actual Behavior

Devices won't sync and a "Changes Pending" is triggered.

[dstokesf5]

Thank you for reporting this. I have added it to our internal product backlog as AUTOTOOL-1393.

[Ahmedmagddi]

Is there any update on this?

[sunitharonan]

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

[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.