You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing the DO API to push configs multiple times, we are seeing some issues with the STATUS in RUNNING state for an eternity. Eventually the API call fails with error tryUntil: max tries reached: Device not active.
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration:
Can't post the entire JSON as its confidential info.
Observe the following error response:
{'id': 'xxxx', 'selfLink': 'https://localhost/mgmt/shared/declarative-onboarding/task/<task-id>', 'code': 500, 'status': 'ERROR', 'message': 'invalid config - rolled back', 'errors': ['tryUntil: max tries reached: Device not active.', 'tryUntil: max tries reached: Device not active.'],
Expected Behavior
Configs pushed fine with success message on the check STATUS API call.
Actual Behavior
the check STATUS API call goes on a forever loop and eventually fails after 5-10 minutes with the above error.
The text was updated successfully, but these errors were encountered:
Environment
Summary
When testing the DO API to push configs multiple times, we are seeing some issues with the STATUS in RUNNING state for an eternity. Eventually the API call fails with error
tryUntil: max tries reached: Device not active.
Steps To Reproduce
Steps to reproduce the behavior:
Can't post the entire JSON as its confidential info.
{'id': 'xxxx', 'selfLink': 'https://localhost/mgmt/shared/declarative-onboarding/task/<task-id>', 'code': 500, 'status': 'ERROR', 'message': 'invalid config - rolled back', 'errors': ['tryUntil: max tries reached: Device not active.', 'tryUntil: max tries reached: Device not active.'],
Expected Behavior
Configs pushed fine with success message on the check STATUS API call.
Actual Behavior
the check STATUS API call goes on a forever loop and eventually fails after 5-10 minutes with the above error.
The text was updated successfully, but these errors were encountered: