Forum Discussion
I first thought that was an timeout issue. A transaction's lifespan is 120s by default. If you haven't issued the VALIDATING command within the time, it will disappear. However, querying or VALIDATING the deleted transaction would result in 404 error but with a different message.
{
"apiError": 1,
"code": 404,
"errorStack": [],
"message": "Task not found - ID: 1559714233007109 user: admin"
}
Will you be able to provide more data? How have you created the transaction, added the task(s) and committed. If that's too much to share in the public space, I suggest you to contact F5 support.
- Cory_BlankenshiJun 05, 2019Altostratus
Hi Satoshi,
I performed the following operations in Postman, and below is the HTTP code generated for each request and response:
1) Get a new transaction
Request
POST /mgmt/tm/transaction?= HTTP/1.1
Host: my.f5.com
Content-Type: application/json
Authorization: Basic YWRtaW46YWRtaW4=
User-Agent: PostmanRuntime/7.13.0
Accept: */*
Host: my.f5.com
cookie: BIGIPAuthCookie=1234A123B12341CDE123F1G12H12I1J1KL12345M; BIGIPAuthUsernameCookie=admin; OAMAuthnHintCookie=0@0123456789
accept-encoding: gzip, deflate
content-length: 2
Connection: keep-alive
{}
** I sent an empty payload in the body
Response
{
"transId": 1559746101292603,
"state": "STARTED",
"timeoutSeconds": 120,
"asyncExecution": false,
"validateOnly": false,
"executionTimeout": 300,
"executionTime": 0,
"failureReason": "",
"kind": "tm:transactionstate",
"selfLink": "https://localhost/mgmt/tm/transaction/1559746101292603?ver=13.1.1"
}
2) Check to see if the transaction was created
Request
GET /mgmt/tm/transaction HTTP/1.1
Host: my.f5.com
Authorization: Basic YWRtaW46YWRtaW4=
User-Agent: PostmanRuntime/7.13.0
Accept: */*
Host: my.f5.com
cookie: BIGIPAuthCookie=1234A123B12341CDE123F1G12H12I1J1KL12345M; BIGIPAuthUsernameCookie=admin; OAMAuthnHintCookie=0@0123456789
accept-encoding: gzip, deflate
Connection: keep-alive
Response
{
"items": [
{
"transId": 1559746101292603,
"state": "STARTED",
"timeoutSeconds": 120,
"asyncExecution": false,
"validateOnly": false,
"executionTimeout": 300,
"executionTime": 0,
"failureReason": "",
"kind": "tm:transactionstate",
"selfLink": "https://localhost/mgmt/tm/transaction/1559746101292603?ver=13.1.1"
}
],
"kind": "tm:transactioncollectionstate",
"selfLink": "https://localhost/mgmt/tm/transaction?ver=13.1.1"
}
3) Test transaction by getting some pool information
Request
GET /mgmt/tm/ltm/pool/~Common~splunk_syslog?$select=name,partition HTTP/1.1
Host: my.f5.com
X-F5-REST-Coordination-Id: 1559746101292603
Authorization: Basic YWRtaW46YWRtaW4=
User-Agent: PostmanRuntime/7.13.0
Accept: */*
Host: my.f5.com
cookie: BIGIPAuthCookie=1234A123B12341CDE123F1G12H12I1J1KL12345M; BIGIPAuthUsernameCookie=admin; OAMAuthnHintCookie=0@0123456789
accept-encoding: gzip, deflate
Connection: keep-alive
Response
{
"name": "splunk_syslog",
"partition": "Common"
}
4) Commit the transaction by setting the status to "Validating"
Request
PATCH /mgmt/tm/transaction/1559744293160010 HTTP/1.1
Host: my.f5.com
Content-Type: application/json
Authorization: Basic YWRtaW46YWRtaW4=
User-Agent: PostmanRuntime/7.13.0
Accept: */*
Host: my.f5.com
cookie: BIGIPAuthCookie=1234A123B12341CDE123F1G12H12I1J1KL12345M; BIGIPAuthUsernameCookie=admin; OAMAuthnHintCookie=0@0123456789
accept-encoding: gzip, deflate
content-length: 29
Connection: keep-alive
{
"state": "VALIDATING"
}
Response
{
"code": 404,
"message": "Missing transaction ID for this call.",
"errorStack": [],
"apiError": 2
}
All of these operations were performed within a few seconds of each other. I'm at a loss...