topic Re: cdFMC Invalid version timestamp when deploying in Network Security

cdFMC Invalid version timestamp when deploying

NiclasAndersen — Tue, 27 Feb 2024 10:17:32 GMT

Background story: I have a customer that are deploying over 900 FTD in CDO and i have a python program that configure and deploy the configuration to each device

I have a program that make a bunch of configuration changes using the Cloud delivered FMC API. Sometimes when i try to deploy my configuration to the device i get this error

Request failed: 400 Client Error: 400 for url: https://{tennantname}/api/fmc_config/v1/domain/{deviceUUID}/deployment/deploymentrequests
Response content: b'{"error":{"category":"FRAMEWORK","messages":[{"description":"Invalid version timestamp."}],"severity":"ERROR"}}'
Failed to deploy configuration: 400 Client Error: 400 for url: https://{tennantname}/api/fmc_config/v1/domain/{deviceUUID}/deployment/deploymentrequests

other times the deployment works, i will say it is about 40% of the deployments i get this error on. Is there anyone that have an idea of the reason for that error?

Re: cdFMC Invalid version timestamp when deploying

AHack210 — Wed, 28 Feb 2024 14:13:41 GMT

Hello Niclas,

Can you post a sanitized version of your API request including all headers?

Re: cdFMC Invalid version timestamp when deploying

Raghav Rao DV — Wed, 28 Feb 2024 16:00:50 GMT

HI,

To avoid getting this, you need to get the version provided by calling getdeployabledevices

and sample would look like

{
  "links": {
    "self": "https://<abc>/api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/deployment/deployabledevices?offset=0&limit=25&expanded=true"
  },
  "items": [
    {
      "isDeploying": false,
      "version": "1709131463843",
      "name": "abc",
      "device": {
        "id": "abc",
        "type": "NGFW_HA",
        "name": "abc",
        "keepLocalEvents": false
      },

Hope this helps

Re: cdFMC Invalid version timestamp when deploying

NiclasAndersen — Thu, 29 Feb 2024 14:46:35 GMT

Thank you, i found out that i never checked if my function where i get the version returned the actual version and not None. So i altered my code to handle that scenario and it hasn't failed today on 23 different devices