Closed jgruberf5 closed 4 years ago
Finally errored:
"result" : {
"errors" : [
"tryUntil: max tries reached: tryUntil: max tries reached: 01020036:3: The requested system device (/Common/adc3nic.openstack.grubernet.org) was not found.",
"Cannot read property 'includes' of undefined"
],
"status" : "ERROR",
"class" : "Result",
"message" : "rollback failed",
"code" : 500
}
This is in our internal product backlog as AUTOTOOL-1125.
This issue has been resolved as part of the 1.11.0 release.
Environment
Summary
Notice the VE device name is bigip1, DO thinks it should be looking for the FQDN.
We MUST force the device name to be equal to the FQDN BEFORE we start anything in DO that is dependent on the device name. There an MANY reason the device name might default back to 'bigip1'.
DO does not complete:
restnoded log hanging: ..... Sun, 02 Feb 2020 16:04:35 GMT - finest: [f5-declarative-onboarding: systemHandler.js] tryUntil: retryOrReject: numRemaining: 11 , code: 404 , message: 01020036:3: The requested system device (/Common/adc3nic.openstack.grubernet.org) was not found. ....
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration:
Observe the following error response:
DO just continues to retry... gave up watching after 30+ mins.
[root@adc3nic:Active:Standalone] opt # curl -s http://127.0.0.1:8105/shared/declarative-onboarding | json_pp
Expected Behavior
Set the ConfigSync IP address on the local device.
Actual Behavior
timeout because the device name doesn't match the FQDN which DO resolved as the device name.