f5-declarative-onboarding icon indicating copy to clipboard operation
f5-declarative-onboarding copied to clipboard

Task status change after restnoded process restarted

Open qsoltys opened this issue 4 years ago • 1 comments

Environment

  • Declarative Onboarding Version: 1.15
  • BIG-IP Version: 14.1.2.3

Summary

Before restart restnoded endpoint https://IP/mgmt/shared/declarative-onboarding return

    "id": "d0e5189c-47ce-4b11-9ef0-d68aec4979f7",
    "selfLink": "https://localhost/mgmt/shared/declarative-onboarding/task/d0e5189c-47ce-4b11-9ef0-d68aec4979f7",
    "result": {
        "class": "Result",
        "code": 200,
        "status": "OK",
        "message": "success"

After restnoded restart

    "id": "d0e5189c-47ce-4b11-9ef0-d68aec4979f7",
    "selfLink": "https://localhost/mgmt/shared/declarative-onboarding/task/d0e5189c-47ce-4b11-9ef0-d68aec4979f7",
    "result": {
        "class": "Result",
        "code": 202,
        "status": "RUNNING",
        "message": "processing"

This generate problem ex. in terraform when information about resource are referred. ex.

Error: Error while Sending/fetching http request :{"id":"295a7297-3f65-41c4-95dd-36053a1656ab","selfLink":"https://localhost/mgmt/shared/declarative-onboarding/task/295a7297-3f65-41c4-95dd-36053a1656ab","result":{"class":"Result","code":202,"status":"RUNNING","message":"processing"},"declaration":{"schemaVersion":"1.0.0","class":"Device","async":true,

Expected Behavior

Task status doesn’t change.

Actual Behavior

Task status change after restart process restnoded.

qsoltys avatar Nov 30 '20 12:11 qsoltys

Confirmed. Added to our internal product backlog as AUTOTOOL-2080. Thank you for reporting the issue.

dstokesf5 avatar Jan 28 '21 00:01 dstokesf5