GTM CLI - The API Call Marks the Run a Success, even when the Actual Traffic Routing is still in Progress (or Stuck)

[sagardeo2105]

Version: 0.4.0
Maximum Parallel Requests to a single domain: 3

We have Job that uses CLI to trigger the GTM Traffic routing.
We use the –complete flag so that the job does not send success message before it completes the routing in Akamai GTM.

But last week we observed multiple times, that the Job completed and marked itself successful with below message:

{
"changeId": "96d6ebd5-de14-4a57-9cf4-8c225dc2b7dc",
"links": [
{
"rel": "self",
"href": "https://akab-*****.luna.akamaiapis.net/config-gtm/v1/domains/domainName/status/current"
}
],
"message": "Change Pending",
"passingValidation": true,
"propagationStatus": "PENDING",
"propagationStatusDate": "2023-05-04T11:57:04.000+00:00"
}

Command used:

"akamai gtm --section default --edgerc .edgerc update-property $DOMAIN_NAME $PROPERTY_NAME
-target '{"datacenterId": $DC_BE_PROD1,"weight": $DC_BE_PROD1_WEIGHT,"enabled":true}'
-target '{"datacenterId": $DC_BE_GCP,"weight": $DC_BE_GCP_WEIGHT,"enabled":true}'
-target '{"datacenterId": $DC_BE_AZURE,"weight": $DC_BE_AZURE_WEIGHT,"enabled":true}'
--verbose --json --complete"

In order to fix this, we could not just retry again with the same routing options, as the CLI could not detect any change from previous request. So, we had to select a different configuration and then again select the desired option.

Since we're using the --complete flag, this job should not have completed in the first place. It should have either failed or remained in progress until the change was actually complete.

[dstopka]

Hi @sagardeo2105,

Thanks for reporting this issue. We'll investigate it and once we know more about it, we'll revert back to you.

Best regards,
Darek