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
Describe the bug
Using the citrixadc_rebooter towards a VPX on SDX fails with one of the following errors.
However - The VPX is rebooted, but the terraform project breaks since other resources depend on a reboot.
Error: [ERROR] nitro-go: Failed to apply action on resource of type reboot, action= err=Post "https://10.x.y.z/nitro/v1/config/reboot": EOF
Error: [ERROR] nitro-go: Failed to apply action on resource of type reboot, action= err=Post "https://10.x.y.z/nitro/v1/config/reboot": read tcp 10.z.y.x:60542->10.x,y,z:443: read: connection reset by peer
Expected behaviour
The provider should handle that the VPX is closing/resetting the connection at once when the command is submitted.
Additional context
While trying the same towards a VPX on hyper-v, the problem occured sporadic, might be because of lower network latency running TF and VPX on a single host?
The text was updated successfully, but these errors were encountered:
Bug Report
Describe the bug
Using the citrixadc_rebooter towards a VPX on SDX fails with one of the following errors.
However - The VPX is rebooted, but the terraform project breaks since other resources depend on a reboot.
Error: [ERROR] nitro-go: Failed to apply action on resource of type reboot, action= err=Post "https://10.x.y.z/nitro/v1/config/reboot": EOF
Error: [ERROR] nitro-go: Failed to apply action on resource of type reboot, action= err=Post "https://10.x.y.z/nitro/v1/config/reboot": read tcp 10.z.y.x:60542->10.x,y,z:443: read: connection reset by peer
To Reproduce
resource "citrixadc_rebooter" "tf_rebooter" {
timestamp = "bootstrap-boot"
warm = false
wait_until_reachable = true
reachable_poll_delay = "180s"
}
Expected behaviour
The provider should handle that the VPX is closing/resetting the connection at once when the command is submitted.
Additional context
While trying the same towards a VPX on hyper-v, the problem occured sporadic, might be because of lower network latency running TF and VPX on a single host?
The text was updated successfully, but these errors were encountered: